Triple
T33756933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death on the Nile (play) |
E865002
|
entity |
| Predicate | originalNovelProtagonist |
P32529
|
FINISHED |
| Object | Hercule Poirot |
E246267
|
NE 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: Hercule Poirot | Statement: [Death on the Nile (play), originalNovelProtagonist, Hercule Poirot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNovelProtagonist Context triple: [Death on the Nile (play), originalNovelProtagonist, Hercule Poirot]
-
A.
protagonistBasedOn
Indicates that a fictional work’s main character is modeled on, inspired by, or derived from a particular real or fictional person or entity.
-
B.
protagonistIs
chosen
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
C.
protagonistOrigin
Indicates that one entity is the origin, source, or starting point of the protagonist in a narrative or story.
-
D.
protagonistDefaultName
Indicates that an entity is the default or canonical name assigned to the protagonist in a given work or context.
-
E.
protagonistDescription
Indicates that a text provides a descriptive summary or characterization of the story’s main protagonist.
- F. None of above.
Provenance (4 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_6a035ac41d088190b7e76b93c1410090 |
completed | May 12, 2026, 4:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366e844f6c819098552979bd6db6b4 |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a035a4f290c8190a0101295a38ae8b8 |
completed | May 12, 2026, 4:50 p.m. |
Created at: May 1, 2026, 1:45 a.m.