Triple
T20713080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flight of Fear |
E509095
|
entity |
| Predicate | indoorBuildingType |
P94573
|
FINISHED |
| Object | enclosed metal warehouse-style structure |
—
|
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: enclosed metal warehouse-style structure | Statement: [Flight of Fear, indoorBuildingType, enclosed metal warehouse-style structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorBuildingType Context triple: [Flight of Fear, indoorBuildingType, enclosed metal warehouse-style structure]
-
A.
typeOfBuildingSpace
Indicates the specific kind or category of building space that an entity represents or occupies.
-
B.
hasIndoorType
chosen
Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
-
C.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
D.
indoorOrOutdoor
Indicates whether an activity, event, or entity occurs inside a building (indoors) or outside in open air (outdoors).
-
E.
locatedInBuildingWithFeature
Indicates that something is located in a building that possesses a specified feature or characteristic.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1ce84e48190922db93ed4b5d21b |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:15 p.m.