Triple
T19260556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluto’s satellite system |
E481636
|
entity |
| Predicate | hasApproximateCharonToPlutoMassRatio |
P135096
|
FINISHED |
| Object | 0.12 |
—
|
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: 0.12 | Statement: [Pluto’s satellite system, hasApproximateCharonToPlutoMassRatio, 0.12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateCharonToPlutoMassRatio Context triple: [Pluto’s satellite system, hasApproximateCharonToPlutoMassRatio, 0.12]
-
A.
massRelativeToPluto
Indicates the comparative mass of an entity expressed relative to the mass of Pluto.
-
B.
relativeSizeToPluto
Indicates how the size of one entity compares to the size of Pluto.
-
C.
recognizedAsDwarfPlanetBy
Indicates that one entity is classified or acknowledged as a dwarf planet by a specified authority, organization, or source.
-
D.
isOneOfMostMassiveTransNeptunianObjects
Indicates that the subject is among the most massive known objects located beyond Neptune in the Solar System.
-
E.
hasInclinationRelativeToOrcus
Indicates that one object's orbital inclination is measured or defined relative to the orbit of Orcus.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb890e7c8190beba407f63459382 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:28 p.m.