Triple
T33415573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scream Extractor |
E855704
|
entity |
| Predicate | locatedInScene |
P40
|
FINISHED |
| Object | secret room in Monsters, Inc. factory |
—
|
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: secret room in Monsters, Inc. factory | Statement: [Scream Extractor, locatedInScene, secret room in Monsters, Inc. factory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInScene Context triple: [Scream Extractor, locatedInScene, secret room in Monsters, Inc. factory]
-
A.
hasSceneLocation
Indicates that a scene or event takes place at, or is set in, a specific location.
-
B.
activeInScene
Indicates that an entity is currently present and participating within a particular scene or context.
-
C.
locatedInAttractionScene
Indicates that one entity is situated within or is part of the setting or scene of an attraction.
-
D.
partOfScene
Indicates that one entity functions as a component or element within a larger scene or setting involving another entity.
-
E.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:36 a.m.