Triple
T2883188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bondi Beach |
E59442
|
entity |
| Predicate | hasSurfCondition |
P13023
|
FINISHED |
| Object | consistent surfable waves |
—
|
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: consistent surfable waves | Statement: [Bondi Beach, hasSurfCondition, consistent surfable waves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfCondition Context triple: [Bondi Beach, hasSurfCondition, consistent surfable waves]
-
A.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
B.
hasSeaCondition
chosen
Indicates that an entity is associated with or characterized by a particular state or condition of the sea.
-
C.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
D.
hasBeachSection
Indicates that an area, location, or property includes or is associated with a specific section designated as a beach.
-
E.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe02c238881908f7a349563c388bf |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.