Triple
T11662310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibraltar Constitution Order 2006 |
E277152
|
entity |
| Predicate | referendumMajority |
P73195
|
FINISHED |
| Object | yes vote |
—
|
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: yes vote | Statement: [Gibraltar Constitution Order 2006, referendumMajority, yes vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referendumMajority Context triple: [Gibraltar Constitution Order 2006, referendumMajority, yes vote]
-
A.
referendumResult
chosen
Indicates the outcome or decision reached by voters in a specific referendum.
-
B.
parliamentaryMajority
Indicates that a political party or coalition holds more than half the seats in a parliament, enabling it to control legislative decisions.
-
C.
majoritySeats
Indicates that one party or group holds more than half of the available seats in a governing or decision-making body.
-
D.
referendumYesPercentage
Indicates the percentage of votes cast in favor of the "yes" option in a referendum.
-
E.
majorityVote
Indicates that a decision or outcome is determined by the option receiving more than half of the votes among a group.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d29fdc8190af46b6e2badb1df5 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.