Triple
T35086850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun |
E1012599
|
entity |
| Predicate | orbitalPeriodAroundMilkyWay |
P182563
|
FINISHED |
| Object | about 225–250 million years |
—
|
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: about 225–250 million years | Statement: [Sun, orbitalPeriodAroundMilkyWay, about 225–250 million years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalPeriodAroundMilkyWay Context triple: [Sun, orbitalPeriodAroundMilkyWay, about 225–250 million years]
-
A.
orbitsInMilkyWay
Indicates that one celestial body follows a gravitational orbit within the Milky Way galaxy.
-
B.
distanceFromMilkyWay
Indicates the measured or estimated spatial distance between an entity and the Milky Way galaxy.
-
C.
distanceToMilkyWayCenter
Indicates the measured or calculated spatial distance between an entity and the center of the Milky Way galaxy.
-
D.
spatialRelationToMilkyWay
Indicates the spatial position or orientation of an entity relative to the Milky Way galaxy.
-
E.
milkyWayPassesThrough
Indicates that the specified object or region lies along or intersects the visible band or plane of the Milky Way in the sky.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:01 p.m.