Triple
T32609219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Blair |
E833606
|
entity |
| Predicate | hasOrdinaryVoting |
P195460
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Division of Blair, hasOrdinaryVoting, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrdinaryVoting Context triple: [Division of Blair, hasOrdinaryVoting, yes]
-
A.
hasVotingPower
Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
-
B.
hasVotingStructure
Indicates that an entity possesses a defined system or arrangement governing how votes are cast, counted, and used to make decisions.
-
C.
hasPublicVoting
Indicates that decisions, selections, or evaluations are made through a voting process that is open and accessible to the general public.
-
D.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
E.
hasNumberOfVotingMembers
Indicates the specific count of individuals who hold voting rights within a given group or body.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69fdd2bda90881909aa229194d014ba7 |
completed | May 8, 2026, 12:10 p.m. |
Created at: May 1, 2026, 1:05 a.m.