Triple
T30193104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coruscant |
E767546
|
entity |
| Predicate | orbitalFeature |
P143697
|
FINISHED |
| Object | multiple orbital traffic stations |
—
|
LITERAL FINISHED |
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: multiple orbital traffic stations | Statement: [Coruscant, orbitalFeature, multiple orbital traffic stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalFeature Context triple: [Coruscant, orbitalFeature, multiple orbital traffic stations]
-
A.
hasOrbitalCharacteristic
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
-
B.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
C.
orbitalComponent
chosen
Indicates that one entity is a component or part of another entity’s orbital system or orbital structure.
-
D.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
E.
orbitShape
Indicates the geometric form or path pattern that an orbiting object follows around another body.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f8572f081909dd920b4b55f488b |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:29 p.m.