Triple
T11198853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angourie |
E264988
|
entity |
| Predicate | surfBreakLevel |
P77345
|
FINISHED |
| Object | suitable for 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: suitable for experienced surfers | Statement: [Angourie, surfBreakLevel, suitable for experienced surfers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfBreakLevel Context triple: [Angourie, surfBreakLevel, suitable for experienced surfers]
-
A.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
B.
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.
-
C.
hasBreakwater
Indicates that a structure or location is equipped with or associated with a breakwater that provides protection from waves or erosion.
-
D.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
E.
surfReputation
Indicates the perceived quality or status of someone or something within a surfing-related context, such as skill, credibility, or recognition in the surf community.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c1e9f88190b2b42326aba9d778 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:29 p.m.