Triple
T9842464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agulhas Retroflection |
E239257
|
entity |
| Predicate | typicalRingDiameter |
P48665
|
FINISHED |
| Object | 200–400 km |
—
|
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: 200–400 km | Statement: [Agulhas Retroflection, typicalRingDiameter, 200–400 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRingDiameter Context triple: [Agulhas Retroflection, typicalRingDiameter, 200–400 km]
-
A.
ringType
Indicates the specific kind or category of ring associated with an entity or relationship.
-
B.
typicalCaseDiameter
chosen
Indicates the usual or standard diameter value associated with an object or case in typical conditions.
-
C.
ringRadius
Indicates the size of a ring by specifying the distance from its center to its outer edge.
-
D.
ringsOn
Indicates that one entity encircles or forms a ring around another entity, typically by being placed around it.
-
E.
hasRing
Indicates that one entity possesses, wears, or is characterized by the presence of a 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34e3420819084bb31170e643cd0 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.