Triple
T26672504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croatia–Bosnia and Herzegovina border |
E672371
|
entity |
| Predicate | hasCoastalEnclave |
P196386
|
FINISHED |
| Object | Neum |
—
|
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: Neum | Statement: [Croatia–Bosnia and Herzegovina border, hasCoastalEnclave, Neum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalEnclave Context triple: [Croatia–Bosnia and Herzegovina border, hasCoastalEnclave, Neum]
-
A.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
-
B.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
C.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
D.
hasCoastalMunicipalities
Indicates that a region or higher-level area includes one or more municipalities that are located along a sea or ocean coastline.
-
E.
hasCoastalAdjacentArea
Indicates that one area directly borders or is immediately next to a coastal zone.
- F. None of above. chosen
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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69fe30bb07d08190877539d5aa202d24 |
completed | May 8, 2026, 6:51 p.m. |
Created at: April 27, 2026, 3:13 a.m.