Triple
T2023228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyprus Sovereign Base Areas |
E44149
|
entity |
| Predicate | hasCivilianPopulation |
P8838
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cyprus Sovereign Base Areas, hasCivilianPopulation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCivilianPopulation Context triple: [Cyprus Sovereign Base Areas, hasCivilianPopulation, yes]
-
A.
isCivilian
Indicates that an entity is a non-military, non-combatant individual in the context of a given situation or system.
-
B.
hasCivilianControl
Indicates that one party exercises authority or oversight over another in a civilian (non-military) capacity.
-
C.
hasPermanentHumanPopulation
chosen
Indicates that an entity consistently hosts a stable, long-term community of human residents rather than only temporary or transient occupants.
-
D.
civilianImpact
Indicates the extent to which an action, event, or situation affects civilians, especially in terms of harm, disruption, or other consequences.
-
E.
civilianTarget
Indicates that the action or operation is directed at, affects, or designates civilians or civilian objects as the target.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f1728481909ae36e821b9edef2 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.