Triple
T4682223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goderdzi Pass |
E103829
|
entity |
| Predicate | winterAccessibility |
P38722
|
FINISHED |
| Object | often difficult due to snow |
—
|
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: often difficult due to snow | Statement: [Goderdzi Pass, winterAccessibility, often difficult due to snow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winterAccessibility Context triple: [Goderdzi Pass, winterAccessibility, often difficult due to snow]
-
A.
winterStatus
chosen
Indicates the condition, phase, or circumstances associated with the winter season for a given entity or context.
-
B.
winterCharacteristic
Indicates a characteristic, feature, or quality that is specifically associated with or typical of winter.
-
C.
winterAscentFirstBy
Indicates that the referenced ascent is the first successful climb of a route, peak, or face carried out specifically in winter conditions by the specified climber or party.
-
D.
hasSnowAndIce
Indicates that the subject is covered with or contains both snow and ice.
-
E.
accessible
Indicates that one entity can be reached, entered, used, or understood by another entity, often without undue difficulty or barriers.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.