Triple
T17226211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Λευκά Όρη |
E418119
|
entity |
| Predicate | hasCoastalSide |
P85982
|
FINISHED |
| Object | Libyan Sea side to the south |
—
|
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: Libyan Sea side to the south | Statement: [Λευκά Όρη, hasCoastalSide, Libyan Sea side to the south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalSide Context triple: [Λευκά Όρη, hasCoastalSide, Libyan Sea side to the south]
-
A.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
B.
hasCoastOnOtherSide
Indicates that one geographic entity has a coastline located on the opposite side of another referenced geographic feature or boundary.
-
C.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
D.
hasCoastalSection
chosen
Indicates that a geographic entity includes at least one section of land that directly borders a sea or ocean.
-
E.
hasCoastalCharacteristic
Indicates that an entity possesses a feature, quality, or condition specifically related to coastal or shoreline environments.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42de1674c81909ca9e87fa9153640 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.