Triple
T33714489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1878 Cyprus Convention |
E863830
|
entity |
| Predicate | effectOnCyprus |
P192083
|
FINISHED |
| Object | beginning of British administration of Cyprus |
—
|
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: beginning of British administration of Cyprus | Statement: [1878 Cyprus Convention, effectOnCyprus, beginning of British administration of Cyprus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnCyprus Context triple: [1878 Cyprus Convention, effectOnCyprus, beginning of British administration of Cyprus]
-
A.
significanceForGreece
Indicates that something holds particular importance, impact, or relevance specifically in the context of Greece.
-
B.
resultEffectOnBrexit
Indicates the effect or impact that a particular result has on Brexit.
-
C.
effectOnCanada
Indicates that one entity has an impact, influence, or consequence on Canada.
-
D.
impactOnByzantines
Indicates the effect or influence that something has on the Byzantines.
-
E.
resultEffectOnIceland
Indicates how a particular event, action, or condition impacts or influences Iceland as an outcome or consequence.
- F. None of above. chosen
Provenance (4 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 1, 2026, 1:44 a.m.