Triple
T19940112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annan Plan for Cyprus |
E479286
|
entity |
| Predicate | dateOfReferendums |
P10273
|
FINISHED |
| Object | 24 April 2004 |
—
|
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: 24 April 2004 | Statement: [Annan Plan for Cyprus, dateOfReferendums, 24 April 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfReferendums Context triple: [Annan Plan for Cyprus, dateOfReferendums, 24 April 2004]
-
A.
referendumDate
chosen
Indicates the specific date on which a referendum is scheduled to or did take place.
-
B.
legalStatusOfReferendums
Indicates the legal status or validity assigned to specific referendums within a given legal or constitutional framework.
-
C.
referendumEvent
Indicates that an event is a referendum, i.e., a formal process in which eligible participants vote directly to accept or reject a specific proposal or decision.
-
D.
plebisciteHeldInYear
Indicates that a plebiscite (a direct vote by the electorate on a specific issue) was held in the specified year.
-
E.
referendumRelated
Indicates a relationship where something is connected to, associated with, or arising from a referendum process or its outcomes.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a1a8df4819094e84855465df6c0 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.