Triple
T9387257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereign Base Areas |
E225934
|
entity |
| Predicate | residentsInclude |
P44546
|
FINISHED |
| Object | Cypriot civilians |
—
|
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: Cypriot civilians | Statement: [Sovereign Base Areas, residentsInclude, Cypriot civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residentsInclude Context triple: [Sovereign Base Areas, residentsInclude, Cypriot civilians]
-
A.
usedForResidentsOf
Indicates that something is intended to be used by, or serves the needs of, people who reside in a particular place or region.
-
B.
hasNonHumanResident
Indicates that a place or location is inhabited or occupied by one or more non-human entities.
-
C.
occupants
chosen
Indicates that certain entities are currently inhabiting, residing in, or using a particular place, space, or object.
-
D.
permanentResidents
Indicates that one entity is a long-term, officially recognized resident of another entity (such as a place, institution, or jurisdiction).
-
E.
returnOfResidents
Indicates the event or process in which residents come back to a place or community where they previously lived.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d562a48190875d9fe3aae25a2b |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.