Triple
T35734621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyros municipality |
E1032852
|
entity |
| Predicate | governsCoastlineOn |
P73457
|
FINISHED |
| Object | Aegean Sea |
E12277
|
NE 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 | Statement: [Skyros municipality, governsCoastlineOn, Aegean Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsCoastlineOn Context triple: [Skyros municipality, governsCoastlineOn, Aegean Sea]
-
A.
coastlineGovernorate
Indicates that a governorate has a coastline or borders a sea or ocean.
-
B.
hasCoastManagement
Indicates that an entity is responsible for or involved in the management, regulation, or oversight of coastal areas or coastal resources in relation to another entity or region.
-
C.
coastlineAssociation
Indicates an association between an entity and a coastline, such as adjacency, alignment, or functional connection to that coastal boundary.
-
D.
isCoastalAuthority
chosen
Indicates that an entity has official jurisdiction or regulatory authority over a coastal area or coastline.
-
E.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
- F. None of above.
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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a02008fcf1c8190b5b6c285944c52e9 |
completed | May 11, 2026, 4:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387cfbfe1481909c137d14fd821da1 |
completed | June 22, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_6a01ffd3ba008190b6f026bd4e6b9a37 |
completed | May 11, 2026, 4:12 p.m. |
Created at: May 3, 2026, 4:05 p.m.