Triple
T23836102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturnian system |
E590856
|
entity |
| Predicate | hasPrimaryExplorer |
P90081
|
FINISHED |
| Object | Cassini spacecraft |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Cassini spacecraft | Statement: [Saturnian system, hasPrimaryExplorer, Cassini spacecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryExplorer Context triple: [Saturnian system, hasPrimaryExplorer, Cassini spacecraft]
-
A.
hasPrimaryHub
Indicates that an entity is associated with or operates from a main or central hub location among potentially multiple hubs.
-
B.
hasPrimary
chosen
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
C.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
D.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
E.
hasPrimaryEnvironment
Indicates that an entity is associated with its main or most characteristic environment or setting.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c882f9148190bb28fe7566ef1e70 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:07 p.m.