Triple
T16531747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorcycle Hill |
E401582
|
entity |
| Predicate | climbingSeasonTypical |
P13215
|
FINISHED |
| Object | late May to early July |
—
|
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: late May to early July | Statement: [Motorcycle Hill, climbingSeasonTypical, late May to early July]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingSeasonTypical Context triple: [Motorcycle Hill, climbingSeasonTypical, late May to early July]
-
A.
climbingSeason
Indicates the period during which climbing an object, route, or area is typically allowed, feasible, or considered optimal.
-
B.
hasClimbingConditions
Indicates that specific environmental or situational conditions suitable for climbing are present or associated with something.
-
C.
typicalSeasonTiming
chosen
Indicates the usual time period or season during which something normally occurs or is expected to take place.
-
D.
climbingPopularity
Indicates how widely practiced, favored, or in-demand a particular form of climbing or climbing-related activity is among participants.
-
E.
climbingAllowed
Indicates that an entity is permitted to climb onto or up another entity or surface.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed8075c81908ff47396879abd0c |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.