Triple
T23254606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1974 Greek referendum |
E581830
|
entity |
| Predicate | yesOption |
P151548
|
FINISHED |
| Object | republic |
—
|
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: republic | Statement: [1974 Greek referendum, yesOption, republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yesOption Context triple: [1974 Greek referendum, yesOption, republic]
-
A.
yesVotes
Indicates that a specified entity has cast or received affirmative votes in a decision-making or voting context.
-
B.
yesVoteShareQuestion1
Indicates the proportion of total votes that were cast as "yes" in response to question 1.
-
C.
optionedBy
Indicates that the rights to develop, produce, or exploit something (such as a work, property, or asset) have been contractually secured by a particular party.
-
D.
yesVoteShareQuestion2
Indicates the proportion of total votes cast in favor of the "Yes" option on question 2 of a ballot or survey.
-
E.
canChoose
Indicates that an entity has the ability or permission to select one option or entity from among alternatives.
- 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193fadac881908579b5729718ee41 |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:11 p.m.