Triple
T23109215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rab archipelago |
E576267
|
entity |
| Predicate | hasSeaAreaType |
P96414
|
FINISHED |
| Object | coastal archipelago |
—
|
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 archipelago | Statement: [Rab archipelago, hasSeaAreaType, coastal archipelago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaAreaType Context triple: [Rab archipelago, hasSeaAreaType, coastal archipelago]
-
A.
hasSeaAreaName
Indicates that a sea area is associated with and identified by a specific name.
-
B.
appliesToSeaArea
Indicates that something (such as a rule, restriction, or designation) is relevant or valid within a specified sea area.
-
C.
seaAreaIncludes
Indicates that a given sea area geographically contains or encompasses another specified area or feature.
-
D.
hasOceanType
chosen
Indicates that a body of water is classified as belonging to a particular type of ocean or oceanic category.
-
E.
seaAreaCode
Indicates the specific coded maritime or sea area associated with or relevant to an entity.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e0d3d4881908e32837b3fbbb406 |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.