Triple
T7413598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haining |
E171071
|
entity |
| Predicate | tidalBoreHeight |
P58169
|
FINISHED |
| Object | can exceed 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: can exceed 9 meters | Statement: [Haining, tidalBoreHeight, can exceed 9 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tidalBoreHeight Context triple: [Haining, tidalBoreHeight, can exceed 9 meters]
-
A.
hasMaximumTidalBoreHeight
chosen
Indicates that one entity has a specified greatest recorded or expected height of its tidal bore.
-
B.
maximumTsunamiHeight
Indicates the greatest recorded or expected vertical height reached by a tsunami at a given location or event.
-
C.
stormSurgeHeight_feet
Indicates the height of the storm surge, measured in feet, typically above a defined reference level such as normal tide.
-
D.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
E.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c336308190932c14cec5eec25f |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.