Triple
T30670296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Labour MPs |
E780774
|
entity |
| Predicate | notableDecline |
P13888
|
FINISHED |
| Object | 2015 UK general election |
—
|
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 UK general election | Statement: [Scottish Labour MPs, notableDecline, 2015 UK general election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDecline Context triple: [Scottish Labour MPs, notableDecline, 2015 UK general election]
-
A.
notableDeparture
Indicates that an entity has left a position, place, or role in a way that is significant or noteworthy.
-
B.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
C.
notableChange
chosen
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
D.
notableLevel
Indicates the degree or extent to which something is considered notable or significant.
-
E.
notableTurnover
Indicates that an entity has experienced a significant change in its members, staff, or participants over a given period.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:31 p.m.