Triple
T5540997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Edward II |
E145286
|
entity |
| Predicate | completionAfterEvent |
P3117
|
FINISHED |
| Object | deposition and death of Edward II |
—
|
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: deposition and death of Edward II | Statement: [Tomb of Edward II, completionAfterEvent, deposition and death of Edward II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completionAfterEvent Context triple: [Tomb of Edward II, completionAfterEvent, deposition and death of Edward II]
-
A.
closedAfterEvent
Indicates that an entity becomes or is marked as closed following the occurrence of a specified event.
-
B.
completionPeriod
Indicates the time span within which an associated task, process, or obligation must be completed.
-
C.
completedBefore
Indicates that one event or action was fully completed prior to the start or completion of another specified event or action.
-
D.
dissolvedAfterEvent
Indicates that an entity ceased to exist, function, or remain intact as a direct consequence of a specified event occurring beforehand.
-
E.
createdAfterEvent
chosen
Indicates that the creation of one entity occurred after a specified event in time.
- 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fc66cc08190b9b2a62098ecbdb1 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:35 p.m.