Triple
T17378571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Vere family |
E422504
|
entity |
| Predicate | earldomCreated |
P100550
|
FINISHED |
| Object | c. 1141 |
—
|
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: c. 1141 | Statement: [de Vere family, earldomCreated, c. 1141]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earldomCreated Context triple: [de Vere family, earldomCreated, c. 1141]
-
A.
heldEarldom
Indicates that a person possessed and held the noble title and rank of an earl.
-
B.
yearOfCreationOfEarldom
chosen
Indicates the specific year in which a particular earldom was formally created or established.
-
C.
EarlMarshal
Indicates a person holds the office or role of Earl Marshal in relation to a sovereign, state, or ceremonial hierarchy.
-
D.
createdEarlOfNorthumberland
Indicates that an entity conferred or established the title of Earl of Northumberland upon another entity.
-
E.
successorAsEarl
Indicates that one person became the next holder of the title of Earl after another person.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a840cd08190af3385388afb8c8f |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.