Triple
T13308383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lituya Bay |
E316994
|
entity |
| Predicate | hasRecordedWaveRunupHeight |
P41302
|
FINISHED |
| Object | about 524 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: about 524 meters | Statement: [Lituya Bay, hasRecordedWaveRunupHeight, about 524 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordedWaveRunupHeight Context triple: [Lituya Bay, hasRecordedWaveRunupHeight, about 524 meters]
-
A.
waveHeightsCanReach
chosen
Indicates that the heights of waves are capable of attaining or reaching a specified magnitude or level.
-
B.
hasMaximumTidalBoreHeight
Indicates that one entity has a specified greatest recorded or expected height of its tidal bore.
-
C.
maximumStormSurgeHeight
Indicates the greatest vertical height reached by storm-driven sea water above a defined reference level during a storm event.
-
D.
stormSurgeHeight_feet
Indicates the height of the storm surge, measured in feet, typically above a defined reference level such as normal tide.
-
E.
hasWave
Indicates that one entity possesses, exhibits, or is associated with a particular wave or waveform.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.