Triple
T13127200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cordilleran Ice Sheet |
E311874
|
entity |
| Predicate | southernLimitApproximate |
P13333
|
FINISHED |
| Object | northwestern United States |
—
|
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: northwestern United States | Statement: [Cordilleran Ice Sheet, southernLimitApproximate, northwestern United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: southernLimitApproximate Context triple: [Cordilleran Ice Sheet, southernLimitApproximate, northwestern United States]
-
A.
southernBoundaryReference
chosen
Indicates that one entity is used as the reference or defining limit for the southern boundary of another entity.
-
B.
southernmost
Indicates that one entity is located farther to the south than all other comparable entities in a given set or context.
-
C.
isOnSouthernPartOf
Indicates that one entity is located on the southern part or southern region of another entity.
-
D.
isSouthernmostPartOf
Indicates that one entity is the geographically furthest south portion or section of another entity.
-
E.
southernmostClassification
Indicates the classification assigned to the entity that lies furthest to the south among a set of related entities.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819aac388190b59bf43cc6a49d0c |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.