Triple
T33729324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | After the Funeral |
E864228
|
entity |
| Predicate | notableDetective |
P39674
|
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: [After the Funeral, notableDetective, Hercule Poirot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDetective Context triple: [After the Funeral, notableDetective, Hercule Poirot]
-
A.
notableSuspect
Indicates that an individual is a particularly significant or prominent suspect in relation to an event, case, or investigation.
-
B.
notableInvestigator
chosen
Indicates that one entity is a distinguished or prominently recognized investigator or researcher associated with another entity.
-
C.
detectiveType
Indicates that one entity is classified as a particular type or category of detective in relation to another entity.
-
D.
companionOfDetective
Indicates a relationship where one entity serves as the detective’s close associate or partner, typically accompanying and assisting them in their investigative work.
-
E.
hasClericalDetective
Indicates that an entity includes or is associated with a detective who is also a member of the clergy.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366e844f6c819098552979bd6db6b4 |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:44 a.m.