Triple
T60075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Legislature |
E1190
|
entity |
| Predicate | membersElectedBy |
P122
|
FINISHED |
| Object | 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: popular vote | Statement: [Florida Legislature, membersElectedBy, popular vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membersElectedBy Context triple: [Florida Legislature, membersElectedBy, popular vote]
-
A.
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.
-
B.
electedCandidate
Indicates that a particular person has been chosen as the winner in an election for a given position or office.
-
C.
elects
chosen
Indicates that one entity selects or chooses another entity for a position, role, or office, typically through a formal voting process.
-
D.
electoralBase
Indicates the group of voters or supporters that primarily backs or sustains a particular candidate, party, or political movement in elections.
-
E.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
- 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_69a24a552ef88190a0df287d68c65cba |
completed | Feb. 28, 2026, 1:52 a.m. |
| NER | Named-entity recognition | batch_69a250e401288190ba12322c9c5f07c9 |
completed | Feb. 28, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69a24e9f40908190a2f4a2111469b733 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 1:55 a.m.