Triple
T3447868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry of Scotland, Earl of Northumbria |
E72719
|
entity |
| Predicate | reignAsEarlOfNorthumbriaEnd |
P48859
|
FINISHED |
| Object | 1152 |
—
|
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: 1152 | Statement: [Henry of Scotland, Earl of Northumbria, reignAsEarlOfNorthumbriaEnd, 1152]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsEarlOfNorthumbriaEnd Context triple: [Henry of Scotland, Earl of Northumbria, reignAsEarlOfNorthumbriaEnd, 1152]
-
A.
successorAsDukeOfNormandy
Indicates that one person becomes the next holder of the title Duke of Normandy after another person.
-
B.
reignAsDukeOfYorkEnd
Indicates the point in time or event at which an individual’s tenure or rule as Duke of York comes to an end.
-
C.
reignAsKingOfEnglandStart
Indicates the time at which a person begins their reign as King of England.
-
D.
EarlMarshal
Indicates a person holds the office or role of Earl Marshal in relation to a sovereign, state, or ceremonial hierarchy.
-
E.
predecessorAsDukeOfNormandy
Indicates that one entity previously held the title of Duke of Normandy immediately before another entity.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba705d988190b76d905751a337ee |
completed | March 8, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:16 p.m.