Triple
T20067972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elmire |
E499658
|
entity |
| Predicate | sceneInvolves |
P120061
|
FINISHED |
| Object | hiding Orgon under the table |
—
|
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: hiding Orgon under the table | Statement: [Elmire, sceneInvolves, hiding Orgon under the table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sceneInvolves Context triple: [Elmire, sceneInvolves, hiding Orgon under the table]
-
A.
scenes
Indicates that one entity is a scene or setting in which the other entity occurs, appears, or is depicted.
-
B.
partOfScene
Indicates that one entity functions as a component or element within a larger scene or setting involving another entity.
-
C.
sceneRelationship
chosen
Indicates a contextual or spatial relationship that links entities based on how they co-occur or interact within the same scene.
-
D.
notableScene
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
E.
sceneLabel
Indicates the categorical label or type assigned to an entire scene based on its overall content or context.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6637ac3fc8190911063b979c3afb8 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.