Triple
T37347448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renfrewshire South |
E927216
|
entity |
| Predicate | previousMspTermEnd |
P100319
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Renfrewshire South, previousMspTermEnd, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousMspTermEnd Context triple: [Renfrewshire South, previousMspTermEnd, 2016]
-
A.
previousMPTermEndYear
Indicates the calendar year in which the subject’s immediately preceding term as a Member of Parliament ended.
-
B.
previousMsp
Indicates that one entity was the immediately preceding managed service provider (MSP) for another entity in a sequence of such providers.
-
C.
previousMLATermStartYear
Indicates the calendar year in which the immediately preceding MLA term for a given entity began.
-
D.
endOfRecalledTerm
Indicates that a recalled or previously referenced term concludes or reaches its endpoint at the specified point or boundary.
-
E.
previousPostEndDate
chosen
Indicates the date on which the immediately preceding post, position, or assignment ended.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:16 p.m.