Triple
T37371388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Canyon trail |
E927851
|
entity |
| Predicate | avoidSeason |
P187790
|
FINISHED |
| Object | midday summer heat |
—
|
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: midday summer heat | Statement: [Red Canyon trail, avoidSeason, midday summer heat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avoidSeason Context triple: [Red Canyon trail, avoidSeason, midday summer heat]
-
A.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
B.
restrictedBySeason
Indicates that the applicability or availability of something is limited or controlled based on a specific time of year or season.
-
C.
visitSeason
Indicates the time of year or season during which a visit or visitation typically occurs.
-
D.
retreatSeason
Indicates the time of year during which a retreat customarily takes place or is scheduled.
-
E.
peakSeasonReason
Indicates that there is a specific cause or justification for why a given time period is considered the peak season for something.
- F. None of above. chosen
Provenance (4 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.