Triple
T14974929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinos Port |
E373419
|
entity |
| Predicate | maritimeArea |
P2975
|
FINISHED |
| Object | Aegean Sea ferry routes |
—
|
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: Aegean Sea ferry routes | Statement: [Tinos Port, maritimeArea, Aegean Sea ferry routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeArea Context triple: [Tinos Port, maritimeArea, Aegean Sea ferry routes]
-
A.
marineArea
chosen
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
-
B.
marineAreaShare
Indicates the proportion of a larger marine area that is occupied, controlled, or otherwise attributed to a specific entity.
-
C.
seaAreaDesignation
Indicates the specific legal or administrative sea area classification that has been assigned to a given marine region.
-
D.
seaAreaA1Definition
Indicates the defined spatial extent or boundary description of a specific sea area labeled A1.
-
E.
maritimeDomain
Indicates a relationship or activity that occurs within, affects, or is specifically associated with the maritime domain (seas, oceans, and related maritime operations).
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e8733081908e06b53746eb6eb6 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:51 a.m.