Triple
T96237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | congressional district method |
E1937
|
entity |
| Predicate | reliesOn |
P1022
|
FINISHED |
| Object | statewide popular vote |
—
|
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: statewide popular vote | Statement: [congressional district method, reliesOn, statewide popular vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reliesOn Context triple: [congressional district method, reliesOn, statewide popular vote]
-
A.
hasDependency
chosen
Indicates that one entity relies on or requires another entity in order to function, exist, or be fulfilled.
-
B.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
-
C.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
D.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
E.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a250cb400c8190b56343bbe19b48c7 |
completed | Feb. 28, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69a24ebd19c48190bab291fea0ecc0c2 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.