Triple
T4452704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Dooley |
E97649
|
entity |
| Predicate | narrativeOutcome |
P40708
|
FINISHED |
| Object | Execution of Tom Dula |
—
|
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: Execution of Tom Dula | Statement: [Tom Dooley, narrativeOutcome, Execution of Tom Dula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeOutcome Context triple: [Tom Dooley, narrativeOutcome, Execution of Tom Dula]
-
A.
narrativeConsequence
chosen
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
-
B.
narrativeStatus
Indicates the role or state of an element within a narrative, such as whether it is current, hypothetical, background, or otherwise positioned in the story’s progression.
-
C.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
-
D.
narrativePremise
Indicates the foundational situation, conflict, or setup that initiates and drives the narrative’s events.
-
E.
narrativeGoal
Indicates that one entity has a desired outcome or objective within a story or narrative context that drives their actions or development.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355f49dc081908727af81b886c08d |
completed | March 13, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.