Triple
T31326721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas le Despenser, 1st Earl of Gloucester |
E798906
|
entity |
| Predicate | wasCreatedEarlBy |
P37514
|
FINISHED |
| Object | Richard II of England |
—
|
NE NERFINISHED |
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: Richard II of England | Statement: [Thomas le Despenser, 1st Earl of Gloucester, wasCreatedEarlBy, Richard II of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCreatedEarlBy Context triple: [Thomas le Despenser, 1st Earl of Gloucester, wasCreatedEarlBy, Richard II of England]
-
A.
createdEarlBy
chosen
Indicates that an entity was granted or established as an earl by a specific creator or authority.
-
B.
createdEarlOfWestmorlandBy
Indicates that a person or authority conferred or established the title "Earl of Westmorland" upon a specific individual.
-
C.
yearOfCreationOfEarldom
Indicates the specific year in which a particular earldom was formally created or established.
-
D.
createdEarlOfNorthumberland
Indicates that an entity conferred or established the title of Earl of Northumberland upon another entity.
-
E.
createdDukeOfNorfolkBy
Indicates that one entity conferred or established the title of Duke of Norfolk upon another entity.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:15 p.m.