Triple
T32449137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encke Gap |
E829229
|
entity |
| Predicate | ringRegion |
P152165
|
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: [Encke Gap, ringRegion, A ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ringRegion Context triple: [Encke Gap, ringRegion, A ring]
-
A.
ringArea
Indicates the area of a ring-shaped region, typically defined by the space between two concentric boundaries.
-
B.
hasRingRegion
chosen
Indicates that one entity possesses or includes a ring-shaped region as part of its structure or spatial extent.
-
C.
ringOrigin
Indicates the source or starting point from which a ring (such as a circular structure, feature, or formation) arises or is generated.
-
D.
ringContained
Indicates that one ring-shaped object is entirely enclosed within the spatial bounds of another ring-shaped object.
-
E.
ringRadius
Indicates the size of a ring by specifying the distance from its center to its outer edge.
- 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_69f6c2e822a88190a7b32d03127a2025 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:56 a.m.