Triple
T36351808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talking to the Dead |
E895223
|
entity |
| Predicate | protagonistAgeDescriptor |
P94896
|
FINISHED |
| Object | young |
—
|
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: young | Statement: [Talking to the Dead, protagonistAgeDescriptor, young]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistAgeDescriptor Context triple: [Talking to the Dead, protagonistAgeDescriptor, young]
-
A.
protagonistAge
Indicates the age of the main character or central figure in a narrative or scenario.
-
B.
characterAgeDescriptor
chosen
Indicates how a character’s age is qualitatively described or categorized (e.g., young, middle-aged, elderly) rather than given as a specific number.
-
C.
hasAgeingProtagonist
Indicates that the work features a main character who is experiencing aging or the later stages of life as a central aspect of their role or development.
-
D.
protagonistDescription
Indicates that a text provides a descriptive summary or characterization of the story’s main protagonist.
-
E.
protagonistAgeDifferenceTheme
Indicates that the work thematically explores the significance or impact of age differences involving the protagonist.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.