Triple
T7908316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaliningrad Oblast |
E183630
|
entity |
| Predicate | isExclave |
P10271
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kaliningrad Oblast, isExclave, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExclave Context triple: [Kaliningrad Oblast, isExclave, true]
-
A.
hasExclave
chosen
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.
wasExclaveOf
Indicates that a territory or region was geographically separated from its main governing state and politically belonged to that state as an exclave.
-
C.
notableEnclave
Indicates that one place is a distinct, noteworthy enclave located within or surrounded by another area or community.
-
D.
leftEnclave
Indicates that one entity has departed from or exited an enclave associated with another entity.
-
E.
containsEnclave
Indicates that one region or territory fully surrounds and encloses another distinct region or territory as an enclave.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a59de00819099f1ce02bb469e75 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:03 p.m.