Triple
T19260625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/2011 (134340) 1 |
E481637
|
entity |
| Predicate | hasNumberOfKnownMoonsInSystem |
P22288
|
FINISHED |
| Object | one of five known moons of Pluto |
—
|
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: one of five known moons of Pluto | Statement: [S/2011 (134340) 1, hasNumberOfKnownMoonsInSystem, one of five known moons of Pluto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfKnownMoonsInSystem Context triple: [S/2011 (134340) 1, hasNumberOfKnownMoonsInSystem, one of five known moons of Pluto]
-
A.
hasNumberOfKnownMoons
Indicates the relationship that specifies how many moons are known to orbit a given celestial body.
-
B.
hasApproximateNumberOfKnownMoons
Indicates that an entity is associated with an estimated or non-exact count of moons known to orbit it.
-
C.
numberOfMoons
Indicates the quantity of moons that an astronomical body possesses.
-
D.
numberOfKnownMoons
chosen
Indicates the count of moons that are currently known to orbit a given celestial body.
-
E.
hasNaturalSatellite
Indicates that one celestial body is orbited by another body that occurs naturally as its satellite.
- 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_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. |
Created at: April 10, 2026, 1:28 p.m.