Triple
T24222093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ralph Neville, 1st Earl of Westmorland |
E601486
|
entity |
| Predicate | creationOfEarldomYear |
P100550
|
FINISHED |
| Object | 1397 |
—
|
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: 1397 | Statement: [Ralph Neville, 1st Earl of Westmorland, creationOfEarldomYear, 1397]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creationOfEarldomYear Context triple: [Ralph Neville, 1st Earl of Westmorland, creationOfEarldomYear, 1397]
-
A.
yearOfCreationOfEarldom
chosen
Indicates the specific year in which a particular earldom was formally created or established.
-
B.
creationOfDukedomDate
Indicates the date on which a particular dukedom was formally created or established.
-
C.
heldEarldom
Indicates that a person possessed and held the noble title and rank of an earl.
-
D.
createdEarlOfNorthumberland
Indicates that an entity conferred or established the title of Earl of Northumberland upon another entity.
-
E.
monarchDuringCreationOfLinkedEarldom
Indicates that the subject was the reigning monarch at the time when the referenced earldom was created.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287dc0b388190bcbbf3f7c61e421d |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, midnight