Triple
T25638624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erinome |
E642773
|
entity |
| Predicate | meanDistanceFromJupiter |
P45907
|
FINISHED |
| Object | about 23 million km |
—
|
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 23 million km | Statement: [Erinome, meanDistanceFromJupiter, about 23 million km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meanDistanceFromJupiter Context triple: [Erinome, meanDistanceFromJupiter, about 23 million km]
-
A.
hasMeanDistanceFromJupiter
chosen
Indicates that one entity has a specified average distance from the planet Jupiter.
-
B.
closestApproachDistanceToJupiter
Indicates the minimum distance an object comes to Jupiter during its trajectory or orbit.
-
C.
relationToJupiter
Indicates a spatial or conceptual relationship that an entity has with the planet Jupiter, such as position, distance, or association relative to it.
-
D.
radiusRelativeToJupiter
Indicates that the radius of one object is expressed as a value relative to the radius of Jupiter.
-
E.
distanceFromPluto
Indicates the measured or calculated spatial distance between a given entity and the celestial body Pluto.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa64332081909df65f8b4380f152 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 5:38 p.m.