Triple
T14352802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin Tennant, 3rd Baron Glenconner |
E355895
|
entity |
| Predicate | titleSuccessionYear |
P34991
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [Colin Tennant, 3rd Baron Glenconner, titleSuccessionYear, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleSuccessionYear Context triple: [Colin Tennant, 3rd Baron Glenconner, titleSuccessionYear, 1983]
-
A.
successionYear
chosen
Indicates the calendar year in which one entity formally succeeded or took over from another in a given role, position, or status.
-
B.
successionLawChangeYear
Indicates the year in which a change to the rules or laws governing succession took effect.
-
C.
successorTitle
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
D.
successorAdoptionYear
Indicates the year in which a successor entity formally adopted or took over from its predecessor.
-
E.
dateOfSuccession
Indicates the specific date on which one entity formally succeeded or took over a role, position, or title from another.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8f4ff1e48190bd9419d70098cede |
completed | April 14, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.