Triple
T26711852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Pitt Glacier |
E673437
|
entity |
| Predicate | isOnFlanksOf |
P20134
|
FINISHED |
| Object | Garibaldi Névé icefield |
—
|
NE NERFINISHED |
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: Garibaldi Névé icefield | Statement: [South Pitt Glacier, isOnFlanksOf, Garibaldi Névé icefield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnFlanksOf Context triple: [South Pitt Glacier, isOnFlanksOf, Garibaldi Névé icefield]
-
A.
liesOnFlankOf
chosen
Indicates that one entity is positioned along the side or lateral edge of another entity.
-
B.
wasOnSideOf
Indicates that one entity supported, aligned with, or took the same side as another entity in a conflict, dispute, or opposing situation.
-
C.
liesOnBorderOf
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
D.
frontLineBetween
Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
-
E.
allianceFlank
Indicates a cooperative maneuver where allied entities position themselves on the side of a common target or objective to gain a tactical advantage.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617c196b48190bdd2734be9dbdc81 |
completed | May 2, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:35 a.m.