Triple
T13897751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winnifred Beach |
E334132
|
entity |
| Predicate | hasTypeOfWaves |
P39320
|
FINISHED |
| Object | generally gentle |
—
|
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: generally gentle | Statement: [Winnifred Beach, hasTypeOfWaves, generally gentle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfWaves Context triple: [Winnifred Beach, hasTypeOfWaves, generally gentle]
-
A.
hasWave
Indicates that one entity possesses, exhibits, or is associated with a particular wave or waveform.
-
B.
waveType
chosen
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
C.
numberOfWaves
Indicates the count of distinct wave events or oscillations associated with a given entity or interaction.
-
D.
hasWaveConsistency
Indicates that the related entities maintain a stable, coherent pattern or behavior across successive waves, phases, or iterations.
-
E.
waveCharacteristic
Indicates that one entity specifies or describes a particular property or feature of a wave associated with another entity.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25d72c6c819093bf9c43136839d4 |
completed | April 14, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.