Triple
T23438500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Katia (2011) |
E565331
|
entity |
| Predicate | surfImpactLocation |
P152282
|
FINISHED |
| Object | U.S. East Coast beaches |
—
|
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: U.S. East Coast beaches | Statement: [Hurricane Katia (2011), surfImpactLocation, U.S. East Coast beaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfImpactLocation Context triple: [Hurricane Katia (2011), surfImpactLocation, U.S. East Coast beaches]
-
A.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
B.
isPartOfSurfArea
Indicates that one area or region is contained within or belongs to a larger surf area.
-
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.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
E.
involvedLandingBeach
Indicates that an entity (such as a military unit, vessel, or operation) participated in or was associated with activities at a specific landing beach.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5dda7448190b6c686e0db4f4f2f |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:50 p.m.