Triple
T2621407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Development Bank |
E59014
|
entity |
| Predicate | votingPowerBasis |
P13230
|
FINISHED |
| Object | subscribed capital shares |
—
|
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: subscribed capital shares | Statement: [Asian Development Bank, votingPowerBasis, subscribed capital shares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingPowerBasis Context triple: [Asian Development Bank, votingPowerBasis, subscribed capital shares]
-
A.
votingBasis
chosen
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
B.
electoralBasis
Indicates the principle, rule, or criterion by which representatives or officials are chosen in an election.
-
C.
hasVotingPower
Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
-
D.
publicVoteWeight
Indicates that an entity’s influence or impact in a public voting process is quantified by a specific weight or value.
-
E.
electoralBase
Indicates the group of voters or supporters that primarily backs or sustains a particular candidate, party, or political movement in 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.