Triple
T31695672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republican Party presidential nomination in 1920 |
E808910
|
entity |
| Predicate | campaignSloganAssociated |
P86825
|
FINISHED |
| Object | Return to Normalcy |
E259119
|
NE 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: Return to Normalcy | Statement: [Republican Party presidential nomination in 1920, campaignSloganAssociated, Return to Normalcy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignSloganAssociated Context triple: [Republican Party presidential nomination in 1920, campaignSloganAssociated, Return to Normalcy]
-
A.
campaignSloganProponents
Indicates that certain entities advocate for, support, or promote a particular campaign slogan.
-
B.
sloganConcept
Indicates that a particular concept, idea, or theme is expressed or represented by a given slogan.
-
C.
sloganGivenBy
Indicates that a particular slogan is provided, coined, or assigned by a specific entity.
-
D.
sloganForm
chosen
Indicates that one entity serves as the slogan or advertising catchphrase associated with another entity.
-
E.
sloganUsedIn
Indicates that a particular slogan is employed or featured within a specific context, such as a campaign, advertisement, or organization.
- F. None of above.
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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b84c5f2f8819084a16dac74bd134e |
completed | June 12, 2026, 4:02 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:10 p.m.