Triple
T29085860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia de Odeceixe |
E734109
|
entity |
| Predicate | hasTypicalWaves |
P194073
|
FINISHED |
| Object | moderate to strong Atlantic swell |
—
|
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: moderate to strong Atlantic swell | Statement: [Praia de Odeceixe, hasTypicalWaves, moderate to strong Atlantic swell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalWaves Context triple: [Praia de Odeceixe, hasTypicalWaves, moderate to strong Atlantic swell]
-
A.
hasWave
Indicates that one entity possesses, exhibits, or is associated with a particular wave or waveform.
-
B.
numberOfWaves
Indicates the count of distinct wave events or oscillations associated with a given entity or interaction.
-
C.
hasWaveQuality
Indicates that something possesses a characteristic or behavior analogous to a wave, such as oscillation, periodicity, or wave-like form.
-
D.
hasWaveShape
Indicates that one entity exhibits or possesses a particular wave-like geometric or physical shape in relation to another.
-
E.
waveType
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
| PDg | Predicate description generation | batch_69fd5f2903a48190ac4b718bff99c6cf |
completed | May 8, 2026, 3:57 a.m. |
Created at: April 28, 2026, 11 a.m.