Triple
T4627193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanmon Straits |
E101126
|
entity |
| Predicate | hasTidalCurrents |
P1735
|
FINISHED |
| Object | 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: strong tidal currents | Statement: [Kanmon Straits, hasTidalCurrents, strong tidal currents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTidalCurrents Context triple: [Kanmon Straits, hasTidalCurrents, strong tidal currents]
-
A.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
B.
isTidal
chosen
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
C.
oceanCurrent
Indicates the flow of seawater in a consistent direction driven by factors like wind, temperature, and salinity.
-
D.
hasSeaCondition
Indicates that an entity is associated with or characterized by a particular state or condition of the sea.
-
E.
isShallowSea
Indicates that a body of water is a shallow marine area, typically near coasts or continental shelves, rather than deep ocean.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a2e9780819081add547c760abc9 |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.