Triple
T19260557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluto’s satellite system |
E481636
|
entity |
| Predicate | hasBarycenterLocation |
P57013
|
FINISHED |
| Object | outside Pluto’s physical radius |
—
|
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: outside Pluto’s physical radius | Statement: [Pluto’s satellite system, hasBarycenterLocation, outside Pluto’s physical radius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBarycenterLocation Context triple: [Pluto’s satellite system, hasBarycenterLocation, outside Pluto’s physical radius]
-
A.
hasBarycenter
Indicates that one entity serves as the barycenter (center of mass) of another entity or system.
-
B.
barycenterLocatedInside
Indicates that the barycenter (center of mass) of one object or system lies within the spatial boundaries of another object or region.
-
C.
hasCenterIn
Indicates that something is located, based, or primarily focused within a specified central place or area.
-
D.
centerOfMassLocation
chosen
Indicates the spatial position at which the total mass of an object or system can be considered to be concentrated.
-
E.
hasCenterType
Indicates that something is characterized by or assigned a specific type or category of center.
- 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.