Triple
T27979127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyprus–United Kingdom relations |
E706570
|
entity |
| Predicate | colonialAnnexationYear |
P9430
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [Cyprus–United Kingdom relations, colonialAnnexationYear, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialAnnexationYear Context triple: [Cyprus–United Kingdom relations, colonialAnnexationYear, 1914]
-
A.
annexedInYear
chosen
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
-
B.
annexationDate
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
-
C.
colonizationStartYear
Indicates the year in which a process of colonization of a place or territory began.
-
D.
conquestYear
Indicates the year in which one entity successfully conquered or took control over another entity.
-
E.
colonizedInCentury
Indicates that an entity established a colony or began colonizing another place during a specified century.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 7:43 p.m.