Triple
T25544414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | murder of Don Andrea |
E640257
|
entity |
| Predicate | isPivotalEventIn |
P112366
|
FINISHED |
| Object | The Spanish Tragedy |
—
|
NE NERFINISHED |
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: The Spanish Tragedy | Statement: [murder of Don Andrea, isPivotalEventIn, The Spanish Tragedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPivotalEventIn Context triple: [murder of Don Andrea, isPivotalEventIn, The Spanish Tragedy]
-
A.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
isMajorEventOf
chosen
Indicates that an event is a primary, significant, or defining occurrence within the context of another entity (such as a project, period, or process).
-
C.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
D.
isLandmarkEvent
Indicates that an event is recognized as a significant or notable occurrence, often marking an important milestone or turning point.
-
E.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f896f04c81908294db99385b464e |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:28 p.m.