Triple
T4589628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hangzhou Bay |
E103450
|
entity |
| Predicate | hasMaximumTidalBoreHeight |
P58169
|
FINISHED |
| Object | up to about 9 meters |
—
|
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 9 meters | Statement: [Hangzhou Bay, hasMaximumTidalBoreHeight, up to about 9 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumTidalBoreHeight Context triple: [Hangzhou Bay, hasMaximumTidalBoreHeight, up to about 9 meters]
-
A.
maximumTsunamiHeight
Indicates the greatest recorded or expected vertical height reached by a tsunami at a given location or event.
-
B.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
C.
waterfallHeight
Indicates the vertical distance or drop in elevation from the top to the bottom of a waterfall.
-
D.
minimumWaterDepthAboveCrest
Indicates the smallest required depth of water that must be maintained above the crest level of a structure or feature.
-
E.
maximumWaterDepth
Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
- 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_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. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:11 p.m.