Triple
T28435409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thorong La |
E715248
|
entity |
| Predicate | typicalTrekkingSeason |
P193190
|
FINISHED |
| Object | March–April |
—
|
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: March–April | Statement: [Thorong La, typicalTrekkingSeason, March–April]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTrekkingSeason Context triple: [Thorong La, typicalTrekkingSeason, March–April]
-
A.
bestSeasonForTrekking
Indicates that a particular season is the most suitable or optimal time for trekking in a given place or context.
-
B.
climbingSeason
Indicates the period during which climbing an object, route, or area is typically allowed, feasible, or considered optimal.
-
C.
hasHikingSeason
chosen
Indicates that there is a specific time period or season during which hiking is typically possible, allowed, or recommended for a given place or trail.
-
D.
typicalSeasonTiming
Indicates the usual time period or season during which something normally occurs or is expected to take place.
-
E.
bestHikingMonths
Indicates the months of the year during which hiking conditions are considered most favorable for a given place or trail.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a00a602b6b48190a9dea8ae22d2fa05 |
completed | May 10, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_6a00a559bf3881909a7b50776d8f47bb |
completed | May 10, 2026, 3:33 p.m. |
Created at: April 28, 2026, 1:42 a.m.