Triple
T707274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Cornwall |
E14127
|
entity |
| Predicate | previousHolderEndDate |
P4346
|
FINISHED |
| Object | 2022-09-08 |
—
|
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: 2022-09-08 | Statement: [Duke of Cornwall, previousHolderEndDate, 2022-09-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHolderEndDate Context triple: [Duke of Cornwall, previousHolderEndDate, 2022-09-08]
-
A.
lastHolder
Indicates that the subject is the most recent entity to have possessed, owned, or held the object.
-
B.
officeholderEndTime
chosen
Indicates the time or date at which a person’s term in a particular office or position comes to an end.
-
C.
firstHolderEnd
Indicates that the specified entity is the one who initially held something and that this holding relationship has come to an end.
-
D.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
E.
formerNamePeriodEnd
Indicates the point in time when an entity stopped using a former name.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5c011948190b2cfccd8fe722742 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f0217081908268b3f47e72f8df |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.