Triple
T5201748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariel |
E117407
|
entity |
| Predicate | parentPlanetMassInfluence |
P52435
|
FINISHED |
| Object | tidally locked to 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: tidally locked to Uranus | Statement: [Ariel, parentPlanetMassInfluence, tidally locked to Uranus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentPlanetMassInfluence Context triple: [Ariel, parentPlanetMassInfluence, tidally locked to Uranus]
-
A.
massRelativeToEarth
Indicates the comparative amount of mass an entity has relative to the mass of Earth.
-
B.
associatedPlanet
chosen
Indicates a relationship where one entity is linked or connected to a particular planet, typically as its relevant or corresponding planetary body.
-
C.
relativeSizeToEarth
Indicates the comparative size of an entity when measured relative to the size of Earth.
-
D.
massRelativeToJupiter
Indicates the mass of an entity expressed as a ratio or multiple of Jupiter’s mass.
-
E.
massRelativeToPluto
Indicates the comparative mass of an entity expressed relative to the mass of 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_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. |
Created at: March 20, 2026, 1:47 p.m.