Triple
T12647123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William de Bohun, 1st Earl of Northampton |
E302054
|
entity |
| Predicate | createdEarlOfNorthampton |
P106171
|
FINISHED |
| Object | 1337 |
—
|
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: 1337 | Statement: [William de Bohun, 1st Earl of Northampton, createdEarlOfNorthampton, 1337]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdEarlOfNorthampton Context triple: [William de Bohun, 1st Earl of Northampton, createdEarlOfNorthampton, 1337]
-
A.
createdEarlOfNorthumberland
Indicates that an entity conferred or established the title of Earl of Northumberland upon another entity.
-
B.
createdEarlOfNottinghamDate
Indicates the date on which the title of Earl of Nottingham was created or conferred.
-
C.
createdDukeOfSomersetDate
Indicates the date on which an entity was made Duke of Somerset.
-
D.
successorAsEarlOfNorthumbria
Indicates that one entity became the next Earl of Northumbria following another entity in succession.
-
E.
successorAsEarlOfHuntingdon
Indicates that one person became the next Earl of Huntingdon following another person in that title or office.
- F. None of above. chosen
Provenance (4 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:17 p.m.