Triple
T32449216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daphnis |
E829231
|
entity |
| Predicate | orbitsNearRingOuterEdge |
P148384
|
FINISHED |
| Object | A ring |
—
|
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: A ring | Statement: [Daphnis, orbitsNearRingOuterEdge, A ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitsNearRingOuterEdge Context triple: [Daphnis, orbitsNearRingOuterEdge, A ring]
-
A.
orbitsWithinRing
Indicates that one celestial body follows an orbital path that lies entirely within the defined ring region of another object.
-
B.
orbitsNear
chosen
Indicates that one object travels around another along a path that remains relatively close in spatial proximity.
-
C.
isOnOuterCircle
Indicates that one entity is positioned on the outer boundary or perimeter of a circular arrangement relative to another entity or reference point.
-
D.
positionInRingSystem
Indicates the specific location or ordering of an object within a ring system relative to the system’s central body and/or other ring components.
-
E.
isOuterRingComparedTo
Indicates that one entity is positioned in an outer ring relative to another entity, which lies in an inner or more central ring.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:56 a.m.