Triple
T26513774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billabong Pro Tahiti |
E669757
|
entity |
| Predicate | breakDirection |
P161020
|
FINISHED |
| Object | left-hand |
—
|
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: left-hand | Statement: [Billabong Pro Tahiti, breakDirection, left-hand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakDirection Context triple: [Billabong Pro Tahiti, breakDirection, left-hand]
-
A.
breakType
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
-
B.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
C.
breaksOn
Indicates that one entity fractures, shatters, or fails when subjected to contact with or force from another entity.
-
D.
break
Indicates that one entity causes another entity to separate into pieces, stop functioning, or otherwise lose its normal integrity or continuity.
-
E.
breaksOver
Indicates that one entity moves or crashes forcefully onto the surface or boundary of another entity, typically dispersing or shattering upon contact.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61394b50c81909e628b2e5b1aa3d5 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 1:22 a.m.