Triple
T18433668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagkadas basin |
E450335
|
entity |
| Predicate | proximityToCoast |
P17623
|
FINISHED |
| Object | relatively close to the Thermaic Gulf |
—
|
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: relatively close to the Thermaic Gulf | Statement: [Lagkadas basin, proximityToCoast, relatively close to the Thermaic Gulf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityToCoast Context triple: [Lagkadas basin, proximityToCoast, relatively close to the Thermaic Gulf]
-
A.
distanceFromCoast
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
B.
hasNearbyCoast
chosen
Indicates that one location is situated close to a coastline or seashore.
-
C.
positionRelativeToCoast
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
D.
basedOnCoast
Indicates that something is situated along, adjacent to, or directly influenced by a coastline.
-
E.
stateOnNearestShore
Indicates that an entity is located on the shore that is geographically closest to another specified reference point or 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b1915d88190a1ecd81cd78ee7d2 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:27 a.m.