Triple
T32288771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Source |
E824905
|
entity |
| Predicate | waveBreakType |
P56828
|
FINISHED |
| Object | reef break |
—
|
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: reef break | Statement: [La Source, waveBreakType, reef break]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waveBreakType Context triple: [La Source, waveBreakType, reef break]
-
A.
waveType
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
B.
breakType
chosen
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
-
C.
waveCondition
Indicates that a specified action, state, or relationship holds only under certain wave-related conditions or patterns.
-
D.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
E.
breakDirection
Indicates the direction in which something breaks, splits, or fractures relative to a reference point or orientation.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd31dc488190aac7229e92312390 |
completed | May 3, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:44 a.m.