Triple
T17281224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Marshal, 5th Earl of Pembroke |
E419532
|
entity |
| Predicate | reignAsEarlOfPembrokeStart |
P126603
|
FINISHED |
| Object | 1241 |
—
|
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: 1241 | Statement: [Walter Marshal, 5th Earl of Pembroke, reignAsEarlOfPembrokeStart, 1241]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsEarlOfPembrokeStart Context triple: [Walter Marshal, 5th Earl of Pembroke, reignAsEarlOfPembrokeStart, 1241]
-
A.
reignAsEarlOfHuntingdonStart
Indicates the time or event at which a person begins their tenure or rule as the Earl of Huntingdon.
-
B.
reignAsEarlOfNorthumbriaStart
Indicates the time at which a person begins their tenure ruling in the position of Earl of Northumbria.
-
C.
successorAsEarlOfPembroke
Indicates that one entity became the next holder of the title Earl of Pembroke after another entity.
-
D.
predecessorAsEarlOfPembroke
Indicates that one entity previously held the title of Earl of Pembroke immediately before another entity, establishing a direct succession in that earldom.
-
E.
reignAsDukeOfBrittanyStart
Indicates the point in time when an individual begins their tenure or rule as the Duke of Brittany.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e43329904c8190a4cbc856b9b94ff8 |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e3874077948190acf5706cfe917d29 |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:40 a.m.