Triple
T29686362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Zevgari |
E751095
|
entity |
| Predicate | isMaritimeNavigationPoint |
P120233
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cape Zevgari, isMaritimeNavigationPoint, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMaritimeNavigationPoint Context triple: [Cape Zevgari, isMaritimeNavigationPoint, true]
-
A.
isNavigationalAid
Indicates that one entity serves as a navigational aid or guide to help locate, orient, or move toward another entity or destination.
-
B.
isPartOfMaritimeZone
Indicates that one area or feature is contained within, or legally belongs to, a specified maritime zone.
-
C.
hasMaritimeFeature
Indicates that one entity possesses, contains, or is characterized by a maritime-related feature such as a sea, coast, harbor, or other oceanic element.
-
D.
isMaritimeRoute
Indicates that one location is connected to another by a navigable sea or ocean route used for maritime transport.
-
E.
isBoatingLandmark
chosen
Indicates that a location serves as a notable reference point or feature specifically used for boating navigation or activities.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67290d2a88190808bbb1528a5d895 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:13 p.m.