Triple
T13207414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tallow Beach |
E314398
|
entity |
| Predicate | hasRipCurrents |
P85723
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tallow Beach, hasRipCurrents, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRipCurrents Context triple: [Tallow Beach, hasRipCurrents, yes]
-
A.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
B.
hasSeaCondition
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.
hasSurfEvent
Indicates that a surf-related event is associated with or occurs at a given entity.
-
E.
shoreHas
chosen
Indicates that a shore possesses, contains, or is characterized by a particular feature, object, or attribute.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9cb7ac819095cff8699993c419 |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.