Triple
T37347446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renfrewshire South |
E927216
|
entity |
| Predicate | previousMspParty |
P194607
|
FINISHED |
| Object | Scottish Labour Party |
—
|
NE NERFINISHED |
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: Scottish Labour Party | Statement: [Renfrewshire South, previousMspParty, Scottish Labour Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousMspParty Context triple: [Renfrewshire South, previousMspParty, Scottish Labour Party]
-
A.
currentMspParty
Indicates that a given political party is the one to which a current Member of the Scottish Parliament (MSP) belongs.
-
B.
previousMsp
Indicates that one entity was the immediately preceding managed service provider (MSP) for another entity in a sequence of such providers.
-
C.
lastMPParty
Indicates the political party with which a member of parliament was most recently affiliated.
-
D.
previousHolderParty
chosen
Indicates that a party previously held a particular role, position, or asset before the current holder.
-
E.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
- 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_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
Created at: May 3, 2026, 4:16 p.m.