Triple
T33756932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death on the Nile (play) |
E865002
|
entity |
| Predicate | originalNovelSetting |
P45019
|
FINISHED |
| Object | 1930s Egypt |
—
|
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: 1930s Egypt | Statement: [Death on the Nile (play), originalNovelSetting, 1930s Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNovelSetting Context triple: [Death on the Nile (play), originalNovelSetting, 1930s Egypt]
-
A.
workOfFictionSetting
Indicates that a work of fiction is set in, or primarily takes place within, a particular location, time, or environment.
-
B.
fictionalStreetSetting
Indicates that an entity is set on or associated with a street that exists only within a fictional or imaginary context.
-
C.
laterSettingOfFiction
Indicates that one fictional work is set chronologically later than another within a shared narrative or story world.
-
D.
placeOfSetting
Indicates the location or environment where an event, scene, or situation takes place.
-
E.
narrativeSettingOfWork
chosen
Indicates that a particular place, time, or context serves as the narrative setting in which a work’s story or events occur.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0358c946f08190a8fb41c643074475 |
completed | May 12, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_6a03586e5bb08190a71e075fde7cd679 |
completed | May 12, 2026, 4:42 p.m. |
Created at: May 1, 2026, 1:45 a.m.