Triple
T25412555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noah Clay |
E636740
|
entity |
| Predicate | deathSceneFeature |
P159438
|
FINISHED |
| Object | distorted facial expression |
—
|
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: distorted facial expression | Statement: [Noah Clay, deathSceneFeature, distorted facial expression]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathSceneFeature Context triple: [Noah Clay, deathSceneFeature, distorted facial expression]
-
A.
deathSceneWork
Indicates that a creative work features or depicts the scene in which a character dies.
-
B.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
C.
deathSceneQuote
Indicates that the quoted text is spoken or presented during a character’s death scene.
-
D.
deathLeadsTo
Indicates that one entity’s death causes, results in, or brings about another event, state, or condition.
-
E.
deathDescribedBy
Indicates that a death event is documented, characterized, or explained by a specific description or source.
- F. None of above. chosen
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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b00ec484819082b3cdcccbd933c3 |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 1:55 p.m.