Triple
T12228711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Hong Kong Chief Executive election |
E291419
|
entity |
| Predicate | votesForJohnLee |
P5054
|
FINISHED |
| Object | 1416 |
—
|
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: 1416 | Statement: [2022 Hong Kong Chief Executive election, votesForJohnLee, 1416]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votesForJohnLee Context triple: [2022 Hong Kong Chief Executive election, votesForJohnLee, 1416]
-
A.
voteFor
chosen
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
B.
voteCount
Indicates the number of votes that have been cast for or associated with a particular item or option.
-
C.
yesVotes
Indicates that a specified entity has cast or received affirmative votes in a decision-making or voting context.
-
D.
votesOnly
Indicates that an entity participates in a decision-making process solely by casting votes, without engaging in any other associated actions or roles.
-
E.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.