Triple

T28477097
Position Surface form Disambiguated ID Type / Status
Subject Enosis movements in Cyprus E720591 entity
Predicate keyEvent P259 FINISHED
Object 1931 Cyprus revolt
The 1931 Cyprus revolt was an anti-colonial uprising by Greek Cypriots against British rule, driven largely by demands for union (Enosis) with Greece.
E1819549 NE 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: 1931 Cyprus revolt | Statement: [Enosis movements in Cyprus, keyEvent, 1931 Cyprus revolt]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 1931 Cyprus revolt
Triple: [Enosis movements in Cyprus, keyEvent, 1931 Cyprus revolt]
Generated description
The 1931 Cyprus revolt was an anti-colonial uprising by Greek Cypriots against British rule, driven largely by demands for union (Enosis) with Greece.

Provenance (5 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_69f01a5983f48190b7c1b8857245a4f7 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f64ee632a48190a1d4a04384504ea9 completed May 2, 2026, 7:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a16419cf770819098c1b2a3a7df9bee completed May 27, 2026, 12:58 a.m.
NEDg Description generation batch_6a16428c40688190a86a99c8c936de3e completed May 27, 2026, 1:02 a.m.
NED2 Entity disambiguation (via description) batch_6a164322f1148190b37794a5fc54f184 completed May 27, 2026, 1:04 a.m.
Created at: April 28, 2026, 2:53 a.m.