Triple
T31190111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pola Naval Base |
E795154
|
entity |
| Predicate | controlledSeaArea |
P195093
|
FINISHED |
| Object | Northern Adriatic Sea |
—
|
NE NERFINISHED |
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: Northern Adriatic Sea | Statement: [Pola Naval Base, controlledSeaArea, Northern Adriatic Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledSeaArea Context triple: [Pola Naval Base, controlledSeaArea, Northern Adriatic Sea]
-
A.
seaAreaUsed
Indicates that a particular sea area is utilized or occupied for a specific purpose or activity.
-
B.
protectedAreaOnShore
Indicates that a protected area is located on or along a shoreline.
-
C.
appliesToSeaArea
Indicates that something (such as a rule, restriction, or designation) is relevant or valid within a specified sea area.
-
D.
seaAreaDesignation
Indicates the specific legal or administrative sea area classification that has been assigned to a given marine region.
-
E.
marineAreaShare
Indicates the proportion of a larger marine area that is occupied, controlled, or otherwise attributed to a specific 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: April 29, 2026, 9:08 p.m.