Triple
T1058865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkcaldy and Cowdenbeath |
E22858
|
entity |
| Predicate | Gordon BrownTermEnd |
P371
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Kirkcaldy and Cowdenbeath, Gordon BrownTermEnd, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Gordon BrownTermEnd Context triple: [Kirkcaldy and Cowdenbeath, Gordon BrownTermEnd, 2015]
-
A.
primeMinisterTermEnd
chosen
Indicates the date or point in time when a person's tenure as prime minister comes to an end.
-
B.
formerPrimeMinisterMP
Indicates that a person served as a prime minister in the past and also held a position as a member of parliament.
-
C.
hasBritishPrimeMinisterParticipant
Indicates that a given event, activity, or situation involves a person serving as the British Prime Minister as a participant.
-
D.
lastPrimeMinister
Indicates that the subject is the most recent individual to have held the office of prime minister of the object entity.
-
E.
primeMinisterTermStart
Indicates the date on which an individual officially begins serving as prime minister.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4ba6e35ac8190802341c31bda0e3b |
completed | March 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69a4b7340a048190807363f19d17a58f |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.