Triple
T28137782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian independence referendum, 1991 |
E714255
|
entity |
| Predicate | resultNoPercent |
P66702
|
FINISHED |
| Object | 7.7 |
—
|
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: 7.7 | Statement: [Ukrainian independence referendum, 1991, resultNoPercent, 7.7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultNoPercent Context triple: [Ukrainian independence referendum, 1991, resultNoPercent, 7.7]
-
A.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
B.
resultBelow
Indicates that one entity’s result, outcome, or measured value is lower than that of another entity.
-
C.
percentage
Indicates the proportion or share of one quantity relative to another, typically expressed as a value out of 100.
-
D.
noVotesPercentage
chosen
Indicates the proportion of total votes that were cast as "no" in a given decision or election.
-
E.
resultUsage
Indicates how the outcome or result of an action, process, or event is used, applied, or consumed in relation to another entity or context.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 9:51 p.m.