Triple
T27979128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyprus–United Kingdom relations |
E706570
|
entity |
| Predicate | CyprusBecameCrownColony |
P99749
|
FINISHED |
| Object | 1925 |
—
|
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: 1925 | Statement: [Cyprus–United Kingdom relations, CyprusBecameCrownColony, 1925]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CyprusBecameCrownColony Context triple: [Cyprus–United Kingdom relations, CyprusBecameCrownColony, 1925]
-
A.
broughtUnderBritishCrown
Indicates that an entity was placed under the authority, control, or sovereignty of the British Crown.
-
B.
reignAsKingOfCyprusFrom
Indicates that a person held and exercised the position and authority of king over Cyprus starting from a specified time.
-
C.
reignStartAsKingOfCyprus
Indicates the date or event marking when an individual began their reign as king of Cyprus.
-
D.
reignAsKingOfCyprusTo
Indicates that a person holds and exercises the position and authority of king over Cyprus.
-
E.
becameRoyalColonyYear
chosen
Indicates the year in which a territory or colony officially transitioned to the status of a royal colony under direct control of the crown.
- 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_69f63b66e9248190974ea3d66f984de1 |
completed | May 2, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:43 p.m.