Triple
T37018137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quiksilver Pro Gold Coast |
E916138
|
entity |
| Predicate | primaryBreak |
P205697
|
FINISHED |
| Object | Snapper Rocks point 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: Snapper Rocks point break | Statement: [Quiksilver Pro Gold Coast, primaryBreak, Snapper Rocks point break]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBreak Context triple: [Quiksilver Pro Gold Coast, primaryBreak, Snapper Rocks point break]
-
A.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
B.
primarySingle
Indicates that an entity has exactly one main or primary association of the specified type, with no additional concurrent primary associations.
-
C.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
D.
primaryCase
Indicates that an entity is the main or leading instance in a set of related cases or occurrences.
-
E.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.