Triple
T4589629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hangzhou Bay |
E103450
|
entity |
| Predicate | hasTidalBoreSpeed |
P56054
|
FINISHED |
| Object | up to about 40 km/h |
—
|
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: up to about 40 km/h | Statement: [Hangzhou Bay, hasTidalBoreSpeed, up to about 40 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTidalBoreSpeed Context triple: [Hangzhou Bay, hasTidalBoreSpeed, up to about 40 km/h]
-
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.
maximumWaterSpeed_kmh
chosen
Indicates the highest speed, measured in kilometers per hour, at which an entity can move through water.
-
C.
isTidal
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
D.
riverbedDepth
Indicates the depth or vertical distance from the water surface to the bottom of a river at a given location or time.
-
E.
maximumTsunamiHeight
Indicates the greatest recorded or expected vertical height reached by a tsunami at a given location or event.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd592232888190af33c47636ca835d |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:11 p.m.