Triple
T17309043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cowell Beach |
E420241
|
entity |
| Predicate | hasTypicalWaveSize |
P54328
|
FINISHED |
| Object | small to medium waves |
—
|
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: small to medium waves | Statement: [Cowell Beach, hasTypicalWaveSize, small to medium waves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalWaveSize Context triple: [Cowell Beach, hasTypicalWaveSize, small to medium waves]
-
A.
hasTypicalMemberSize
Indicates the usual or characteristic size associated with members of a given class or group.
-
B.
hasWave
chosen
Indicates that one entity possesses, exhibits, or is associated with a particular wave or waveform.
-
C.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
D.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
E.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439970cf08190bc9e49ba830da0d9 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.