Triple
T21053003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESSV |
E518635
|
entity |
| Predicate | isInBalticSeaRegion |
P142650
|
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: [ESSV, isInBalticSeaRegion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInBalticSeaRegion Context triple: [ESSV, isInBalticSeaRegion, yes]
-
A.
isBalticPortRegion
Indicates that a region functions as a port area located on or directly connected to the Baltic Sea.
-
B.
isBalticPortCity
Indicates that a city functions as a port located on the Baltic Sea.
-
C.
includesBalticStates
Indicates that the subject set, group, or entity contains or encompasses the Baltic States (typically Estonia, Latvia, and Lithuania).
-
D.
isInNorthernFinland
Indicates that an entity is located within the geographical region of northern Finland.
-
E.
hasNordicArea
Indicates that an entity possesses, includes, or is associated with a geographic area located in the Nordic region.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7cabe881909e6b258a14d501a6 |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:36 p.m.