Triple
T25005057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grayndler |
E625818
|
entity |
| Predicate | hasVotingProfile |
P85910
|
FINISHED |
| Object | strong progressive voting base |
—
|
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: strong progressive voting base | Statement: [Grayndler, hasVotingProfile, strong progressive voting base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVotingProfile Context triple: [Grayndler, hasVotingProfile, strong progressive voting base]
-
A.
hasElectorateProfile
chosen
Indicates that an entity is associated with a specific electorate-related profile describing its voting or demographic characteristics.
-
B.
hasVotingPower
Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
-
C.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
-
D.
hadVoteIn
Indicates that an entity participated by casting a vote in a particular decision, election, or voting event.
-
E.
hasVotingPlatform
Indicates that an entity is associated with or utilizes a particular platform or system for conducting voting or elections.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:05 a.m.