Triple
T5541461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sterope I |
E145298
|
entity |
| Predicate | orbitsInMilkyWay |
P65286
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sterope I, orbitsInMilkyWay, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitsInMilkyWay Context triple: [Sterope I, orbitsInMilkyWay, yes]
-
A.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
B.
interactionWithMilkyWay
Indicates a relationship in which an entity affects, is affected by, or otherwise engages in some form of interaction with the Milky Way galaxy.
-
C.
coOrbitsWith
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
-
D.
orbitsBeyond
Indicates that one celestial body orbits at a greater average distance from a central object than another specified body.
-
E.
impactOnMilkyWay
Indicates the effect or influence that something has on the Milky Way galaxy, such as altering its structure, dynamics, or evolution.
- 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fc66cc08190b9b2a62098ecbdb1 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:35 p.m.