Triple
T15586819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CF |
E374642
|
entity |
| Predicate | usedInPoliticalDiscourse |
P119319
|
FINISHED |
| Object | 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 | Statement: [CF, usedInPoliticalDiscourse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInPoliticalDiscourse Context triple: [CF, usedInPoliticalDiscourse, yes]
-
A.
usedPoliticalStrategy
Indicates that one entity employed a particular political strategy or tactic in relation to another entity or context.
-
B.
usedInPropaganda
Indicates that something is employed as a tool or element within propaganda efforts to influence opinions or behavior.
-
C.
usesPoliticalLabel
Indicates that one entity applies or assigns a specific political label or classification to another entity.
-
D.
usedWithinPoliticalEntityType
Indicates that something is utilized or applied within the context of a specific type or category of political entity (such as a state, city, or region).
-
E.
politicalRhetoric
Indicates that an entity uses language or communication strategically to influence political opinions, attitudes, or actions.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e4900408190aadb48b001db4169 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:11 a.m.