Triple
T2951808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRK.A |
E79836
|
entity |
| Predicate | relativeVotingPowerComparedToBRK.B |
P44299
|
FINISHED |
| Object | higher |
—
|
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: higher | Statement: [BRK.A, relativeVotingPowerComparedToBRK.B, higher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeVotingPowerComparedToBRK.B Context triple: [BRK.A, relativeVotingPowerComparedToBRK.B, higher]
-
A.
publicVoteWeight
Indicates that an entity’s influence or impact in a public voting process is quantified by a specific weight or value.
-
B.
hasVotingPower
Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
-
C.
ballotRelationship
Indicates a relationship in which one entity’s connection to or role within a ballot (such as creation, inclusion, or association with a vote) is specified in relation to another entity.
-
D.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
E.
electoralRank
Indicates the position or level an entity holds within an electoral hierarchy or ranking system.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98fcea5c8190b7d80de942bcb4f7 |
completed | March 8, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:57 p.m.