Triple
T31755083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Dutchman coaster model |
E810535
|
entity |
| Predicate | intendedSensation |
P35696
|
FINISHED |
| Object | flight |
—
|
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: flight | Statement: [Flying Dutchman coaster model, intendedSensation, flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedSensation Context triple: [Flying Dutchman coaster model, intendedSensation, flight]
-
A.
intendedPerception
Indicates that one entity is meant or designed to be perceived (e.g., seen, heard, or otherwise sensed) by another entity.
-
B.
intendedEmotion
Indicates the emotion that an action, expression, or communication is meant to evoke in its target, regardless of the actual emotion experienced.
-
C.
providesSensoryEffects
chosen
Indicates that one entity causes or contributes to sensory experiences or perceptions in another entity.
-
D.
hasSensation
Indicates that an entity experiences or is subject to a particular sensory or perceptual feeling.
-
E.
designedToEvoke
Indicates that something was intentionally created or arranged in order to elicit a particular reaction, feeling, or response from an audience or observer.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 30, 2026, 11:29 p.m.