Triple
T2032479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Glacier |
E44548
|
entity |
| Predicate | locatedOnFace |
P32348
|
FINISHED |
| Object | eastern face of Aconcagua |
—
|
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: eastern face of Aconcagua | Statement: [Polish Glacier, locatedOnFace, eastern face of Aconcagua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnFace Context triple: [Polish Glacier, locatedOnFace, eastern face of Aconcagua]
-
A.
locatedOnBody
chosen
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
B.
faceType
Indicates the specific shape or structural category of a face that an entity possesses or is characterized by.
-
C.
facedBy
Indicates that one entity is oriented toward and directly opposite another entity, such that it is facing it.
-
D.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
E.
faceValueType
Indicates the type or category of a financial instrument’s face (nominal) value, such as how that value is defined or represented.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9313134819088133fb69b8f606f |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.