Triple
T34470210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austral Volcanic Zone |
E884885
|
entity |
| Predicate | isSouthernmostSegmentOf |
P17679
|
FINISHED |
| Object | Andean volcanic chain |
—
|
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: Andean volcanic chain | Statement: [Austral Volcanic Zone, isSouthernmostSegmentOf, Andean volcanic chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSouthernmostSegmentOf Context triple: [Austral Volcanic Zone, isSouthernmostSegmentOf, Andean volcanic chain]
-
A.
isSouthernmostPartOf
chosen
Indicates that one entity is the geographically furthest south portion or section of another entity.
-
B.
isOnSouthernPartOf
Indicates that one entity is located on the southern part or southern region of another entity.
-
C.
isShortestStateSegmentOf
Indicates that one state segment is the minimal-length segment among all segments that could represent that same portion of a state or process.
-
D.
hasSouthernTerminus
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
-
E.
southernmost
Indicates that one entity is located farther to the south than all other comparable entities in a given set or context.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7199dda688190a79d5e73b285f132 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2:01 a.m.