Triple
T5201667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titania |
E117406
|
entity |
| Predicate | averageOrbitalDistanceFromUranus_km |
P62430
|
FINISHED |
| Object | 436300 |
—
|
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: 436300 | Statement: [Titania, averageOrbitalDistanceFromUranus_km, 436300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageOrbitalDistanceFromUranus_km Context triple: [Titania, averageOrbitalDistanceFromUranus_km, 436300]
-
A.
averageOrbitalDistanceFromPluto_km
Indicates the average distance, measured in kilometers, between an entity’s orbit and Pluto’s orbit.
-
B.
averageOrbitalDistanceFromMars_km
Indicates the average distance, in kilometers, between an object’s orbit and the orbit of Mars.
-
C.
distanceFromNeptune
Indicates the measured or calculated spatial separation between a given entity and the planet Neptune.
-
D.
hasMeanDistanceFromJupiter
Indicates that one entity has a specified average distance from the planet Jupiter.
-
E.
averageOrbitalSpeed
Indicates the typical speed at which one celestial body travels along its orbit around another over a complete orbital period.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7ad9bdd88190ae8aa6f4aba695a7 |
completed | March 20, 2026, 4:50 p.m. |
Created at: March 20, 2026, 1:47 p.m.