Triple
T32449215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daphnis |
E829231
|
entity |
| Predicate | orbitsWithinRing |
P174480
|
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, orbitsWithinRing, A ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitsWithinRing Context triple: [Daphnis, orbitsWithinRing, A ring]
-
A.
orbitsInteriorTo
Indicates that one object orbits another along a path that lies entirely within the orbital path of a third, outer reference object.
-
B.
orbitsNear
Indicates that one object travels around another along a path that remains relatively close in spatial proximity.
-
C.
includesOrbitOf
Indicates that one entity’s orbital path or region fully contains or encompasses the orbital path or region of another entity.
-
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.
orbitsUsed
Indicates that one entity utilizes or traverses specific orbital paths associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f6c2e822a88190a7b32d03127a2025 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:56 a.m.