Triple
T8908747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish devolution referendum, 1997 |
E212127
|
entity |
| Predicate | campaignSloganProponents |
P86319
|
FINISHED |
| Object | Yes-Yes |
—
|
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: Yes-Yes | Statement: [Scottish devolution referendum, 1997, campaignSloganProponents, Yes-Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignSloganProponents Context triple: [Scottish devolution referendum, 1997, campaignSloganProponents, Yes-Yes]
-
A.
electoralSlogan
Indicates that a phrase is used as a campaign message or motto to promote a candidate, party, or political cause in an election.
-
B.
campaignSymbol
Indicates that something serves as a symbol or emblem representing a particular campaign.
-
C.
sloganConcept
Indicates that a particular concept, idea, or theme is expressed or represented by a given slogan.
-
D.
campaignTheme
Indicates the central idea or message that characterizes and unifies a particular campaign.
-
E.
campaignPromise
Indicates that an individual or organization has made a public commitment to take a specific action or pursue a particular policy as part of a campaign.
- F. None of above. chosen
Provenance (4 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65207bbc8190be181555b9564797 |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc604965c48190bbb6db0ae8108e67 |
completed | April 1, 2026, 12:01 a.m. |
Created at: March 30, 2026, 6:55 p.m.