Triple
T31702930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodge |
E809103
|
entity |
| Predicate | deathSymbolizes |
P129
|
FINISHED |
| Object | end of the old family order |
—
|
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: end of the old family order | Statement: [Dodge, deathSymbolizes, end of the old family order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathSymbolizes Context triple: [Dodge, deathSymbolizes, end of the old family order]
-
A.
deathMotif
Indicates that a recurring theme, symbol, or narrative element in a work is associated with death or mortality.
-
B.
deathSceneSignificance
Indicates the importance or impact that a particular death scene has within the context of the narrative or overall work.
-
C.
deathInterpretedAs
Indicates that one entity’s death is understood, framed, or interpreted in a particular way by another entity or within a given context.
-
D.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
E.
deathDescribedBy
Indicates that a death event is documented, characterized, or explained by a specific description or source.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 30, 2026, 11:12 p.m.