Triple
T9663313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ifni |
E233639
|
entity |
| Predicate | typeOfEnclave |
P89480
|
FINISHED |
| Object | coastal enclave |
—
|
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: coastal enclave | Statement: [Ifni, typeOfEnclave, coastal enclave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEnclave Context triple: [Ifni, typeOfEnclave, coastal enclave]
-
A.
containsEnclave
Indicates that one region or territory fully surrounds and encloses another distinct region or territory as an enclave.
-
B.
integratedSecureEnclave
Indicates that a system or component includes a built-in secure enclave that isolates and protects sensitive operations or data from the rest of the environment.
-
C.
typeOfCluster
Indicates that one entity is classified as a specific kind or category of cluster in relation to another entity.
-
D.
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.
-
E.
supportsIntelSGX
Indicates that one entity provides compatibility with or functional support for Intel Software Guard Extensions (Intel SGX) used by another entity.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0cde048190b5a8e1548825d4d9 |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:14 p.m.