Triple
T5201686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titania |
E117406
|
entity |
| Predicate | positionBySizeInUranianSystem |
P62431
|
FINISHED |
| Object | largest moon of Uranus |
—
|
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: largest moon of Uranus | Statement: [Titania, positionBySizeInUranianSystem, largest moon of Uranus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionBySizeInUranianSystem Context triple: [Titania, positionBySizeInUranianSystem, largest moon of Uranus]
-
A.
relativeSizeToPluto
Indicates how the size of one entity compares to the size of Pluto.
-
B.
rankByDistanceFromSun
Indicates an ordering of entities based on how close or far they are from the Sun, with position determined by distance.
-
C.
relativeSizeToEarth
Indicates the comparative size of an entity when measured relative to the size of Earth.
-
D.
positionInCosmos
Indicates the spatial or hierarchical location of an entity within the broader structure of the cosmos or universe.
-
E.
radiusRelativeToJupiter
Indicates that the radius of one object is expressed as a value relative to the radius of Jupiter.
- 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.