Triple
T9806611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth–Moon system |
E237968
|
entity |
| Predicate | perigeeDistance_km |
P26358
|
FINISHED |
| Object | about 363300 |
—
|
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 363300 | Statement: [Earth–Moon system, perigeeDistance_km, about 363300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perigeeDistance_km Context triple: [Earth–Moon system, perigeeDistance_km, about 363300]
-
A.
perihelionDistance
Indicates the shortest distance between an orbiting body and the Sun along its orbital path.
-
B.
perigee
chosen
Indicates the point in an object's orbit where it is closest to the body it is orbiting.
-
C.
minimumOrbitIntersectionDistanceWithEarth_au
Indicates the smallest distance, measured in astronomical units, between an object's orbit and Earth's orbit at their closest point of approach.
-
D.
aphelionDistance
Indicates the greatest distance between an orbiting body and the star it orbits, measured at the point of aphelion in its orbit.
-
E.
perihelionDate
Indicates the date on which an orbiting body reaches its closest point to the Sun in its orbital path.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7cb9588190953a063cb7b9e29e |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.