Triple
T19260575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluto’s satellite system |
E481636
|
entity |
| Predicate | hasApproximateNixOrbitalPeriod |
P58578
|
FINISHED |
| Object | 24.9 Earth days |
—
|
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: 24.9 Earth days | Statement: [Pluto’s satellite system, hasApproximateNixOrbitalPeriod, 24.9 Earth days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateNixOrbitalPeriod Context triple: [Pluto’s satellite system, hasApproximateNixOrbitalPeriod, 24.9 Earth days]
-
A.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
B.
hasOrbitalCharacteristic
chosen
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
-
C.
hasAxisOfOrbit
Indicates that an orbiting object is associated with a specific axis around which its orbital motion is defined.
-
D.
orbitalPeriodRange_minutesUpperBound
Indicates the maximum value, in minutes, of the allowed or observed range for an entity’s orbital period.
-
E.
epochOfOrbit
Indicates the specific reference time at which an orbit’s parameters are defined or measured.
- 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.