Triple
T22120698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Off The Wall |
E546657
|
entity |
| Predicate | waveBreaks |
P140299
|
FINISHED |
| Object | right |
—
|
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: right | Statement: [Off The Wall, waveBreaks, right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waveBreaks Context triple: [Off The Wall, waveBreaks, right]
-
A.
waveCondition
Indicates that a specified action, state, or relationship holds only under certain wave-related conditions or patterns.
-
B.
waveType
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
C.
hasBreakwater
Indicates that a structure or location is equipped with or associated with a breakwater that provides protection from waves or erosion.
-
D.
breaksOver
chosen
Indicates that one entity moves or crashes forcefully onto the surface or boundary of another entity, typically dispersing or shattering upon contact.
-
E.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12951fcd48190841319cd879c15cb |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.