Triple
T17120232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Republican primary, 2008 |
E415443
|
entity |
| Predicate | campaignStateImportance |
P17293
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Florida Republican primary, 2008, campaignStateImportance, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignStateImportance Context triple: [Florida Republican primary, 2008, campaignStateImportance, high]
-
A.
politicalImportance
Indicates the degree to which something holds significance, influence, or priority within political processes, decisions, or power structures.
-
B.
importanceInEvent
Indicates the degree to which an entity plays a significant or central role within a particular event.
-
C.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
-
D.
resultImportance
Indicates that one entity specifies how significant, critical, or impactful the outcome or result of another entity is.
-
E.
electoralSignificance
chosen
Indicates the importance or impact that something has on an election’s outcome, dynamics, or results.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e8092b548190b45c1695be47edc2 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.