Triple
T8746041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Ridge route |
E207829
|
entity |
| Predicate | typicalIceDifficulty |
P24163
|
FINISHED |
| Object | AI2-3 |
—
|
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: AI2-3 | Statement: [North Ridge route, typicalIceDifficulty, AI2-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIceDifficulty Context triple: [North Ridge route, typicalIceDifficulty, AI2-3]
-
A.
typicalIceThickness
Indicates the usual or characteristic thickness of ice under normal or representative conditions.
-
B.
iceStrengthened
Indicates that an entity has been made stronger, reinforced, or enhanced through the application or influence of ice.
-
C.
hasTypicalIceRegime
Indicates that there is a characteristic or commonly occurring pattern of ice conditions associated with the referenced entity.
-
D.
hasTrailDifficulty
chosen
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
E.
iceClass
Indicates a classification relationship specifying the level or category of ice-strengthening or ice-navigation capability assigned to a vessel or structure.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d745e0081909cab216593d5c01b |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.