Triple
T22657346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tacitus’ Histories |
E559262
|
entity |
| Predicate | narrativeBeginsWith |
P21329
|
FINISHED |
| Object | death of Nero |
—
|
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: death of Nero | Statement: [Tacitus’ Histories, narrativeBeginsWith, death of Nero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeBeginsWith Context triple: [Tacitus’ Histories, narrativeBeginsWith, death of Nero]
-
A.
narrativeStart
chosen
Indicates the point or event at which a narrative, story, or sequence of events begins.
-
B.
narrativePassage
Indicates that a segment of text functions as a narrative passage, conveying events, actions, or storytelling rather than exposition, dialogue, or other discourse types.
-
C.
narrativePremise
Indicates the foundational situation, conflict, or setup that initiates and drives the narrative’s events.
-
D.
narrativeEndPoint
Indicates the point in a narrative sequence at which the story or described event concludes or reaches its final state.
-
E.
openingNarrativeDevice
Indicates the narrative device or technique used to begin or introduce a story or discourse.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765c62bc8190b3fcde76d6b6dfb6 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:06 p.m.