Triple
T18190773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent Conrad |
E435525
|
entity |
| Predicate | notableVote |
P130162
|
FINISHED |
| Object | supported Affordable Care Act |
—
|
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: supported Affordable Care Act | Statement: [Kent Conrad, notableVote, supported Affordable Care Act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVote Context triple: [Kent Conrad, notableVote, supported Affordable Care Act]
-
A.
notableProposition
Indicates that a subject is associated with a proposition, statement, or claim that is considered notable or significant in some context.
-
B.
notableParty
Indicates that an entity is a significant or noteworthy participant in an event, activity, or relationship.
-
C.
notableBill
Indicates that a bill is especially significant or noteworthy, typically due to its impact, prominence, or public attention.
-
D.
notableCount
Indicates the number of notable or distinguished items, entities, or instances associated with a given subject.
-
E.
notableProposal
Indicates that an entity is a proposal distinguished by particular significance, impact, or recognition compared to other proposals.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0cf0d7c81908ce0386c52ef601d |
completed | April 19, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:31 a.m.