Triple
T31469923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grube |
E802827
|
entity |
| Predicate | hasCoastalProximityTo |
P17623
|
FINISHED |
| Object | Baltic Sea |
E2697
|
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: Baltic Sea | Statement: [Grube, hasCoastalProximityTo, Baltic Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalProximityTo Context triple: [Grube, hasCoastalProximityTo, Baltic Sea]
-
A.
hasNearbyCoast
chosen
Indicates that one location is situated close to a coastline or seashore.
-
B.
hasCoastalAdjacentArea
Indicates that one area directly borders or is immediately next to a coastal zone.
-
C.
hasMaximumDistanceFromCoast
Indicates that an entity is located at the greatest possible distance from any coastline within a specified area or context.
-
D.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
-
E.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0227ce59a081909fe1ba1181d86b4d |
completed | May 11, 2026, 7:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b076c7c448190b51c564573deacde |
completed | June 11, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a02273989208190beb948b8c7bdaee3 |
completed | May 11, 2026, 7 p.m. |
Created at: April 30, 2026, 9:25 p.m.