Triple
T34081941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukhyi Estuary |
E874066
|
entity |
| Predicate | isCoastalLagoonOf |
P178203
|
FINISHED |
| Object | Black Sea |
—
|
NE NERFINISHED |
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: Black Sea | Statement: [Sukhyi Estuary, isCoastalLagoonOf, Black Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoastalLagoonOf Context triple: [Sukhyi Estuary, isCoastalLagoonOf, Black Sea]
-
A.
isLagoon
chosen
Indicates that a body of water is a lagoon, i.e., a shallow coastal or inland water area separated from a larger body of water by a barrier such as a sandbank, reef, or barrier island.
-
B.
isCoastalWetlandCity
Indicates that a city is located within or adjacent to a coastal wetland area, such as marshes, mangroves, or tidal flats.
-
C.
isCoastalOrRiverine
Indicates that a place is located along a sea coast or adjacent to a river, reflecting a shoreline or riverbank relationship.
-
D.
isCoastalTo
Indicates that one place is located along or directly borders the coastline of another body of water or coastal region.
-
E.
isCoastalLocation
Indicates that a location is situated on or directly adjacent to a sea, ocean, or significant coastal body of water.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:52 a.m.