Triple
T3693267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1840 United States presidential election |
E78392
|
entity |
| Predicate | campaignInnovation |
P1484
|
FINISHED |
| Object | mass rallies |
—
|
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: mass rallies | Statement: [1840 United States presidential election, campaignInnovation, mass rallies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignInnovation Context triple: [1840 United States presidential election, campaignInnovation, mass rallies]
-
A.
campaignOrService
Indicates that one entity is a campaign and the other is a service that the campaign promotes, uses, or is associated with.
-
B.
campaignType
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
C.
innovation
chosen
Indicates the introduction or development of something new or significantly improved compared to existing methods, products, or ideas.
-
D.
innovationFrom
Indicates that something originates, arises, or is derived as an innovation from a particular source or prior entity.
-
E.
ledCampaignIn
Indicates that an entity directed or was in charge of organizing and executing a campaign within a particular context or location.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4e89f588190951371439a035850 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.