Triple
T22531438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoebe |
E557044
|
entity |
| Predicate | meanOrbitalDistanceFromSaturn_Mm |
P140761
|
FINISHED |
| Object | 12.95 |
—
|
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: 12.95 | Statement: [Phoebe, meanOrbitalDistanceFromSaturn_Mm, 12.95]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meanOrbitalDistanceFromSaturn_Mm Context triple: [Phoebe, meanOrbitalDistanceFromSaturn_Mm, 12.95]
-
A.
averageOrbitalDistanceFromSaturn_km
Indicates the average distance, measured in kilometers, between an object’s orbit and the planet Saturn.
-
B.
relativePositionFromSaturn
Indicates the spatial position or ordering of one entity as measured or defined relative to the location of Saturn.
-
C.
distanceFromSaturnCloudTops
Indicates the measured or specified distance between an entity and the tops of Saturn’s cloud layer.
-
D.
closestApproachToSaturnDistance
Indicates the minimum distance an object comes to Saturn at its point of closest approach.
-
E.
meanOrbitalRadius_km
chosen
Indicates the average distance, measured in kilometers, between an orbiting body and the center of the object it orbits.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed7625081908bdb6cebcda96712 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.