Triple
T28212303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke (The Notebook character) |
E711205
|
entity |
| Predicate | featuredInSceneSetting |
P54861
|
FINISHED |
| Object | nursing home common room |
—
|
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: nursing home common room | Statement: [Duke (The Notebook character), featuredInSceneSetting, nursing home common room]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredInSceneSetting Context triple: [Duke (The Notebook character), featuredInSceneSetting, nursing home common room]
-
A.
portrayedInSetting
chosen
Indicates that an entity is depicted or represented within a particular setting, environment, or context.
-
B.
performedInScene
Indicates that an action or event took place within a specific scene or setting.
-
C.
partOfScene
Indicates that one entity functions as a component or element within a larger scene or setting involving another entity.
-
D.
isSettingOfScene
Indicates that a particular location, time, or environment serves as the backdrop or context in which a scene takes place.
-
E.
notableSceneProp
Indicates that an object or element serves as a significant or prominently featured prop within a particular scene.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: April 27, 2026, 10:40 p.m.