Triple
T19940111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annan Plan for Cyprus |
E479286
|
entity |
| Predicate | dateOfFinalVersion |
P84305
|
FINISHED |
| Object | 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: 2004 | Statement: [Annan Plan for Cyprus, dateOfFinalVersion, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFinalVersion Context triple: [Annan Plan for Cyprus, dateOfFinalVersion, 2004]
-
A.
dateFinalized
Indicates that a specific date has been set as the official or final completion/confirmation time for an associated event, decision, or record.
-
B.
finalVersionYear
chosen
Indicates the year in which the final or last version of something was completed, released, or became definitive.
-
C.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
-
D.
finalAppTransitionDate
Indicates the date on which the final transition or change of state for the application was completed.
-
E.
developmentDate
Indicates the date on which something was created, developed, or brought into existence.
- 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.