Triple
T33917404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orkan |
E869498
|
entity |
| Predicate | settingOfMainStoryline |
P190297
|
FINISHED |
| Object | Boulder, Colorado (via Mork) |
—
|
NE NERFINISHED |
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: Boulder, Colorado (via Mork) | Statement: [Orkan, settingOfMainStoryline, Boulder, Colorado (via Mork)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfMainStoryline Context triple: [Orkan, settingOfMainStoryline, Boulder, Colorado (via Mork)]
-
A.
mainSettingOfStory
chosen
Indicates that a location or environment serves as the primary setting in which the events of a story take place.
-
B.
settingOfMainOrdeal
Indicates the primary location or environment where the central challenge, conflict, or ordeal of a narrative takes place.
-
C.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
D.
storylineEvent
Indicates that one event occurs as a distinct step or component within a larger narrative or storyline.
-
E.
settingOfAdventure
Indicates that a location or environment serves as the primary setting where an adventure takes place.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 1, 2026, 1:48 a.m.