Triple
T4943250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charon |
E110986
|
entity |
| Predicate | averageOrbitalDistanceFromPluto_km |
P60176
|
FINISHED |
| Object | 19571 |
—
|
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: 19571 | Statement: [Charon, averageOrbitalDistanceFromPluto_km, 19571]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageOrbitalDistanceFromPluto_km Context triple: [Charon, averageOrbitalDistanceFromPluto_km, 19571]
-
A.
closestApproachToPlutoDistance
Indicates the minimum distance an object comes to Pluto at the point of its closest approach.
-
B.
approximateDistanceFromSun
Indicates an estimated or rough measure of how far an entity is from the Sun, rather than an exact distance.
-
C.
averageOrbitalSpeed
Indicates the typical speed at which one celestial body travels along its orbit around another over a complete orbital period.
-
D.
hasMeanDistanceFromSun
Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
-
E.
distanceFromNeptune
Indicates the measured or calculated spatial separation between a given entity and the planet Neptune.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a7650c8190b046b65072fd8eae |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6ff85b50819081d78087caa6b473 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:31 p.m.