Triple
T29255697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Clare |
E741696
|
entity |
| Predicate | lastMaleHeirDiedAt |
P98182
|
FINISHED |
| Object | Battle of Bannockburn |
—
|
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: Battle of Bannockburn | Statement: [House of Clare, lastMaleHeirDiedAt, Battle of Bannockburn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastMaleHeirDiedAt Context triple: [House of Clare, lastMaleHeirDiedAt, Battle of Bannockburn]
-
A.
deathBeforeAccessionAccordingTo
Indicates that one entity’s death occurred before another entity’s accession, as established or reported by a specified source or authority.
-
B.
deathBeforeAccession
Indicates that one entity’s death occurred before another entity’s accession to a position, title, or role.
-
C.
diedDuringReignOf
Indicates that one entity died while another entity was in power or ruling.
-
D.
lastLegitimateMaleHeirOf
chosen
Indicates that one entity is the final male descendant in a legitimate line of succession or inheritance from another entity.
-
E.
endOfReignReason
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664ad3f708190aa20d4224a218c8e |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:37 p.m.