Triple
T27106644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Youngkin gubernatorial campaign, 2021 |
E686595
|
entity |
| Predicate | campaignSloganType |
P54069
|
FINISHED |
| Object | change-focused messaging |
—
|
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: change-focused messaging | Statement: [Youngkin gubernatorial campaign, 2021, campaignSloganType, change-focused messaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignSloganType Context triple: [Youngkin gubernatorial campaign, 2021, campaignSloganType, change-focused messaging]
-
A.
campaignSloganProponents
Indicates that certain entities advocate for, support, or promote a particular campaign slogan.
-
B.
sloganForm
Indicates that one entity serves as the slogan or advertising catchphrase associated with another entity.
-
C.
sloganConcept
Indicates that a particular concept, idea, or theme is expressed or represented by a given slogan.
-
D.
campaignType
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
E.
sloganCategory
chosen
Indicates that a slogan is classified as belonging to a particular category or type.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623fdda548190827d6867bba39de7 |
completed | May 2, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:51 a.m.