Triple
T28429229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabang Beach |
E715071
|
entity |
| Predicate | typicalWaveHeightRange |
P41302
|
FINISHED |
| Object | 1 to 4 feet for beginners |
—
|
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: 1 to 4 feet for beginners | Statement: [Sabang Beach, typicalWaveHeightRange, 1 to 4 feet for beginners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWaveHeightRange Context triple: [Sabang Beach, typicalWaveHeightRange, 1 to 4 feet for beginners]
-
A.
waveHeightsCanReach
chosen
Indicates that the heights of waves are capable of attaining or reaching a specified magnitude or level.
-
B.
hasStrongWavesSometimes
Indicates that the subject occasionally experiences or produces waves that are notably strong or intense.
-
C.
waveMeasurementScale
Indicates the scale or unit system used to quantify a wave-related measurement.
-
D.
hasTypicalWaves
Indicates that something exhibits the usual or characteristic pattern, form, or behavior of waves associated with it.
-
E.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a00a22e32f481909b6006c5b1cdefd3 |
completed | May 10, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a00a1bd9c908190b4aa17a61f48126f |
completed | May 10, 2026, 3:18 p.m. |
Created at: April 28, 2026, 1:38 a.m.