Triple
T563036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strait of Gibraltar |
E13493
|
entity |
| Predicate | oceanographicFeature |
P16223
|
FINISHED |
| Object | site of strong tidal currents |
—
|
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: site of strong tidal currents | Statement: [Strait of Gibraltar, oceanographicFeature, site of strong tidal currents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oceanographicFeature Context triple: [Strait of Gibraltar, oceanographicFeature, site of strong tidal currents]
-
A.
oceanCurrent
Indicates the flow of seawater in a consistent direction driven by factors like wind, temperature, and salinity.
-
B.
oceanBasin
Indicates a relationship where a geographic or marine feature is located within, or is part of, a specific ocean basin.
-
C.
oceanDrainageBasin
Indicates the ocean into which a river system or drainage basin ultimately discharges its water.
-
D.
oceanNamedAfter
Indicates that an ocean bears the name of a particular person, place, or entity in whose honor or reference it is named.
-
E.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a712bc48190ba298b3c76ab11cc |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c044648190a98589ab18935216 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a498ff0c0081908947376a38b10d72 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:32 p.m.