Triple
T545410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Mendocino |
E12720
|
entity |
| Predicate | offshoreFeature |
P15518
|
FINISHED |
| Object | continental shelf |
—
|
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: continental shelf | Statement: [Cape Mendocino, offshoreFeature, continental shelf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offshoreFeature Context triple: [Cape Mendocino, offshoreFeature, continental shelf]
-
A.
coastlineFeature
Indicates that a geographic entity is a specific type of feature located along or forming part of a coastline.
-
B.
hasShoreFeature
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
C.
containsCoastalFeature
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
-
D.
hasCityOnShore
Indicates that a city is located on or directly adjacent to the shore of a body of water.
-
E.
hasOffshoreWindFarm
Indicates that an entity owns, operates, or is otherwise associated with a wind farm located in offshore (marine) areas.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498dfec5c81908b76d723b30dc2f0 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b8098481908097228db8ad0262 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49858abd48190bd4b002a93e4a908 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.