Triple
T9623674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhekelia Garrison |
E232404
|
entity |
| Predicate | borderCharacteristics |
P38214
|
FINISHED |
| Object | includes areas that border the Republic 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: includes areas that border the Republic of Cyprus | Statement: [Dhekelia Garrison, borderCharacteristics, includes areas that border the Republic of Cyprus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCharacteristics Context triple: [Dhekelia Garrison, borderCharacteristics, includes areas that border the Republic of Cyprus]
-
A.
borderCharacteristic
chosen
Indicates that one entity specifies a property, feature, or quality of the border or boundary of another entity.
-
B.
recognizedBorder
Indicates that one entity formally acknowledges and accepts another entity’s boundary as a legitimate border.
-
C.
borderText
Indicates that one entity is the textual content displayed along the border of another entity.
-
D.
borderColor
Indicates the color that forms the boundary or outline of an entity.
-
E.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9ad650a4819096258665bc3f410b |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.