Triple
T1770519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Cádiz |
E38863
|
entity |
| Predicate | hasOceanographicFeature |
P16223
|
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: [Gulf of Cádiz, hasOceanographicFeature, continental shelf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOceanographicFeature Context triple: [Gulf of Cádiz, hasOceanographicFeature, continental shelf]
-
A.
oceanographicFeature
chosen
Indicates that one entity is an oceanographic feature (such as a current, front, eddy, or water mass) associated with or characterizing another entity.
-
B.
hasOcean
Indicates that a geographic region, country, or landmass is bordered by or directly adjacent to a particular ocean.
-
C.
hasOceanCoverage
Indicates that a specified area or region is covered by ocean to a certain extent or proportion.
-
D.
oceanicPortion
Indicates that one entity is a part or segment of an ocean or oceanic area in relation to another entity.
-
E.
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.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.