Triple
T2709753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Khambhat |
E59829
|
entity |
| Predicate | maximumTidalRangeCategory |
P4652
|
FINISHED |
| Object | macrotidal |
—
|
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: macrotidal | Statement: [Gulf of Khambhat, maximumTidalRangeCategory, macrotidal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumTidalRangeCategory Context triple: [Gulf of Khambhat, maximumTidalRangeCategory, macrotidal]
-
A.
hasTidalRange
chosen
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
B.
maximumTsunamiHeight
Indicates the greatest recorded or expected vertical height reached by a tsunami at a given location or event.
-
C.
maximumTsunamiHeightLocation
Indicates the location at which the tsunami reaches its maximum recorded or predicted height.
-
D.
seaLevelCharacteristic
Indicates a characteristic, property, or attribute specifically related to sea level.
-
E.
stormSurgeHeight_feet
Indicates the height of the storm surge, measured in feet, typically above a defined reference level such as normal tide.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda7771a4819081904bd6b818b81b |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.