Triple
T19259952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1604 Tombaugh |
E481619
|
entity |
| Predicate | ascendingNodeLongitude |
P135089
|
FINISHED |
| Object | 176.0 deg |
—
|
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: 176.0 deg | Statement: [1604 Tombaugh, ascendingNodeLongitude, 176.0 deg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ascendingNodeLongitude Context triple: [1604 Tombaugh, ascendingNodeLongitude, 176.0 deg]
-
A.
coordinateLongitude
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
B.
coordinateLatitude
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
-
C.
colongitude
Indicates the angular distance of a point (typically on a rotating body) measured westward from a defined prime meridian, often used to specify its position relative to the body’s rotation or illumination.
-
D.
lunarLatitude
Indicates the angular distance of a point on the Moon north or south of the lunar equator.
-
E.
lunarLongitude
Indicates the angular position of the Moon along its orbital path, measured as longitude relative to a defined reference direction or point.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8858588190a04e2a01e43fb7b2 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:28 p.m.