Triple
T28062949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciskei |
E709163
|
entity |
| Predicate | hadEnclaveExclavePattern |
P164019
|
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: [Ciskei, hadEnclaveExclavePattern, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadEnclaveExclavePattern Context triple: [Ciskei, hadEnclaveExclavePattern, yes]
-
A.
hasExclave
Indicates that a territory or administrative unit possesses an exclave—part of its area that is geographically separated from its main portion and surrounded by foreign territory.
-
B.
containsEnclave
Indicates that one region or territory fully surrounds and encloses another distinct region or territory as an enclave.
-
C.
belongsToExclave
Indicates that one entity is part of, or contained within, a geographically separated exclave of another entity.
-
D.
hasNeighboringExclave
Indicates that one entity possesses an exclave that directly borders or is adjacent to an exclave of another entity.
-
E.
typeOfEnclave
Indicates that one entity is an enclave and specifies the kind or category of enclave it is (e.g., political, cultural, economic).
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 8:41 p.m.