Triple
T15611283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koddiyar Bay |
E375297
|
entity |
| Predicate | hasCoastlineSettlement |
P119430
|
FINISHED |
| Object | Trincomalee District settlements |
—
|
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: Trincomalee District settlements | Statement: [Koddiyar Bay, hasCoastlineSettlement, Trincomalee District settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastlineSettlement Context triple: [Koddiyar Bay, hasCoastlineSettlement, Trincomalee District settlements]
-
A.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
B.
hasCoastlineType
Indicates the specific nature or classification of the coastline associated with a geographic entity.
-
C.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
-
D.
hasCountryCoastline
Indicates that a country possesses a coastline along a sea or ocean.
-
E.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e8148a0819087d6d69cc84487ca |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:13 a.m.