Triple
T4536989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2006 Montenegrin independence referendum |
E107429
|
entity |
| Predicate | yesVotePercentage |
P9216
|
FINISHED |
| Object | approximately 55.5% |
—
|
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: approximately 55.5% | Statement: [2006 Montenegrin independence referendum, yesVotePercentage, approximately 55.5%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yesVotePercentage Context triple: [2006 Montenegrin independence referendum, yesVotePercentage, approximately 55.5%]
-
A.
yesVotes
Indicates that a specified entity has cast or received affirmative votes in a decision-making or voting context.
-
B.
voterTurnoutPercentage
Indicates the proportion of eligible or registered voters who actually cast a ballot in a given election, expressed as a percentage.
-
C.
popularVoteShare
chosen
Indicates the proportion of all votes cast in an election that were received by a particular candidate, party, or option.
-
D.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
E.
voteResult
Indicates the outcome or decision produced by a voting process involving the related entities.
- 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57b78b8481909d79131723d4be22 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.