Triple
T27489760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 Taiwanese presidential election |
E693845
|
entity |
| Predicate | JamesSoongVotes |
P162444
|
FINISHED |
| Object | 4,664,972 |
—
|
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: 4,664,972 | Statement: [2000 Taiwanese presidential election, JamesSoongVotes, 4,664,972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JamesSoongVotes Context triple: [2000 Taiwanese presidential election, JamesSoongVotes, 4,664,972]
-
A.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
B.
yesVotes
Indicates that a specified entity has cast or received affirmative votes in a decision-making or voting context.
-
C.
congressionalVoteRunnerUp
Indicates that an entity finished in second place (runner-up) in a specific congressional vote or election.
-
D.
electoralVoteFor
Indicates that a specified number of electoral votes are allocated or cast in favor of a particular candidate or option in an election.
-
E.
heldElectoralVoteFor
Indicates that an elector or jurisdiction cast its official electoral vote in favor of a particular candidate in an election.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e882cbc81908caa3e8a5fb5c1f4 |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:04 p.m.