Triple
T3098379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taygete |
E64655
|
entity |
| Predicate | hasOrbitalDirection |
P45906
|
FINISHED |
| Object | retrograde |
—
|
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: retrograde | Statement: [Taygete, hasOrbitalDirection, retrograde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalDirection Context triple: [Taygete, hasOrbitalDirection, retrograde]
-
A.
hasOrbitalPlane
Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
-
B.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
C.
onOrbitalRoute
Indicates that one object is currently traveling along or positioned on a defined orbital path around another body.
-
D.
hasOrbitalRegion
Indicates that one entity occupies, lies within, or is associated with a specific orbital zone or region around another body.
-
E.
hasOrbitalStability
Indicates that an object maintains a stable, non-disruptive orbit around another body over time.
- F. None of above. chosen
Provenance (4 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada23dde988190a1aca020685594f3 |
completed | March 8, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ad9df06ed88190809f0683122caa5a |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.