Triple
T18860137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shimon Lankri |
E461289
|
entity |
| Predicate | hasCoastalCityUnderAdministration |
P41457
|
FINISHED |
| Object | Mediterranean Sea coast |
—
|
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: Mediterranean Sea coast | Statement: [Shimon Lankri, hasCoastalCityUnderAdministration, Mediterranean Sea coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalCityUnderAdministration Context triple: [Shimon Lankri, hasCoastalCityUnderAdministration, Mediterranean Sea coast]
-
A.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
-
B.
hasCoastalMunicipalities
chosen
Indicates that a region or higher-level area includes one or more municipalities that are located along a sea or ocean coastline.
-
C.
hasCoastalAdjacentArea
Indicates that one area directly borders or is immediately next to a coastal zone.
-
D.
hasCoastlineSettlement
Indicates that a settlement is located on or directly adjacent to a coastline.
-
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 (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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05fb800819098951ec134a1fa2a |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.