Triple
T1482683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Democratic caucuses 2004 |
E30993
|
entity |
| Predicate | mainTypeOfDelegates |
P24418
|
FINISHED |
| Object | pledged delegates |
—
|
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: pledged delegates | Statement: [Iowa Democratic caucuses 2004, mainTypeOfDelegates, pledged delegates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTypeOfDelegates Context triple: [Iowa Democratic caucuses 2004, mainTypeOfDelegates, pledged delegates]
-
A.
numberOfDelegates
Indicates the quantity of delegates associated with or assigned to a particular entity or event.
-
B.
mayDelegateTo
Indicates that one entity is permitted to transfer or assign its authority, responsibility, or rights to another entity.
-
C.
electsDelegatesTo
Indicates that one entity selects or votes to choose representatives (delegates) who will act or decide on its behalf in another body or process.
-
D.
notableDelegate
Indicates that an entity serves as a significant or distinguished representative or delegate for another entity or group.
-
E.
majorConstituentType
chosen
Indicates the type or category of a primary or dominant component that makes up a larger whole.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c6782f088190930d25a56161e2b3 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.