Triple
T1339778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Minister of Wales |
E28437
|
entity |
| Predicate | firstHolderEndDate |
P17301
|
FINISHED |
| Object | 2000-02-09 |
—
|
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: 2000-02-09 | Statement: [First Minister of Wales, firstHolderEndDate, 2000-02-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHolderEndDate Context triple: [First Minister of Wales, firstHolderEndDate, 2000-02-09]
-
A.
firstHolderEnd
chosen
Indicates that the specified entity is the one who initially held something and that this holding relationship has come to an end.
-
B.
previousHolderStartDate
Indicates the date on which the immediately preceding holder of something (e.g., a position, title, or asset) began their tenure or ownership.
-
C.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
-
D.
lastHolder
Indicates that the subject is the most recent entity to have possessed, owned, or held the object.
-
E.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c21303c881908fef0b32831222fe |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.