Triple
T5075089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo I Dwarf Galaxy |
E114373
|
entity |
| Predicate | orbitsWithinMilkyWayHalo |
P34020
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Leo I Dwarf Galaxy, orbitsWithinMilkyWayHalo, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitsWithinMilkyWayHalo Context triple: [Leo I Dwarf Galaxy, orbitsWithinMilkyWayHalo, true]
-
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.
coOrbitsWith
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
-
C.
MilkyWaySubgroup
Indicates that one astronomical object is a member of the Milky Way subgroup within the Local Group of galaxies.
-
D.
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.
-
E.
isSatelliteGalaxyOf
chosen
Indicates that one galaxy orbits and is gravitationally bound to another, larger host galaxy as its satellite.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d2243481908c1ae62f7123c4e9 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.