Triple
T3320574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Beaconsfield |
E69784
|
entity |
| Predicate | firstHolderDeathYear |
P16526
|
FINISHED |
| Object | 1881 |
—
|
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: 1881 | Statement: [Earl of Beaconsfield, firstHolderDeathYear, 1881]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHolderDeathYear Context triple: [Earl of Beaconsfield, firstHolderDeathYear, 1881]
-
A.
dateOfDeath
Indicates the specific date on which an individual or entity died.
-
B.
notableBearerDeathYear
Indicates the year in which a notable bearer of the referenced name, title, or role died.
-
C.
yearOfDeath
chosen
Indicates the specific year in which an entity (typically a person or organism) died.
-
D.
firstHolderDate
Indicates the date on which an entity first became the holder or owner of another entity (e.g., an asset, title, or right).
-
E.
deathYearApproximate
Indicates that the year of an entity’s death is known only approximately rather than as an exact calendar year.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13b85208190b13aba355d5dafcf |
completed | March 8, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.