Triple
T5129997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenva Glacier |
E115672
|
entity |
| Predicate | hasAvalanchePath |
P27773
|
FINISHED |
| Object | Brenva avalanche path |
—
|
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: Brenva avalanche path | Statement: [Brenva Glacier, hasAvalanchePath, Brenva avalanche path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAvalanchePath Context triple: [Brenva Glacier, hasAvalanchePath, Brenva avalanche path]
-
A.
hasPathway
chosen
Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
-
B.
hasArc
Indicates that there is a directed connection or edge from one entity to another, often representing a link in a graph or network.
-
C.
hasNumberOfConvergingAvenues
Indicates the number of distinct avenues that meet or converge at a particular location or junction.
-
D.
hasValley
Indicates that one entity contains, features, or is characterized by the presence of a valley associated with the other entity.
-
E.
hasEasiestRoute
Indicates that one entity provides or represents the simplest or least difficult route or path to reach another entity or destination.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:42 p.m.