Triple
T19571234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supersuck |
E489719
|
entity |
| Predicate | suitabilityForSurfers |
P77345
|
FINISHED |
| Object | experienced surfers |
—
|
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: experienced surfers | Statement: [Supersuck, suitabilityForSurfers, experienced surfers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suitabilityForSurfers Context triple: [Supersuck, suitabilityForSurfers, experienced surfers]
-
A.
surfingLevelRequired
chosen
Indicates the minimum surfing skill or proficiency level that an entity must have in order to participate in or access another entity or activity.
-
B.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
C.
discoveredAsSurfSpotBy
Indicates that a location became recognized and used as a surf spot through the actions or discovery of a particular person or group.
-
D.
learnsToSurfFrom
Indicates that one entity acquires or practices surfing skills under the instruction, guidance, or example of another entity.
-
E.
isPartOfSurfArea
Indicates that one area or region is contained within or belongs to a larger surf area.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402103208190b80acdfa82b7a9c4 |
completed | April 20, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.