Triple
T735077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States politics |
E14910
|
entity |
| Predicate | hasCampaignFeature |
P182
|
FINISHED |
| Object | primary elections |
—
|
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: primary elections | Statement: [United States politics, hasCampaignFeature, primary elections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampaignFeature Context triple: [United States politics, hasCampaignFeature, primary elections]
-
A.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
C.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
D.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fafee081909bf356854c09aaff |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.