Triple
T36670230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Curious Case of Benjamin Button |
E905390
|
entity |
| Predicate | protagonistEndOfLifeForm |
P186226
|
FINISHED |
| Object | infant |
—
|
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: infant | Statement: [The Curious Case of Benjamin Button, protagonistEndOfLifeForm, infant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistEndOfLifeForm Context triple: [The Curious Case of Benjamin Button, protagonistEndOfLifeForm, infant]
-
A.
mannerOfLifeEnd
Indicates the way or circumstances in which an entity’s life comes to an end.
-
B.
legalStatusAtEndOfLife
Indicates the legal classification or condition that applies to an entity at the time of its termination, dissolution, or death.
-
C.
protagonistLoses
Indicates that the main character in a narrative is defeated, fails, or otherwise does not achieve their primary goal.
-
D.
isTerminallyIll
Indicates that an entity is suffering from an incurable illness expected to lead to death in the relatively near future.
-
E.
afterlifeForm
Indicates the form, state, or manifestation an entity takes in an afterlife or post-mortem existence.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:12 p.m.