Triple
T26152787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ocean Beach, San Diego |
E659872
|
entity |
| Predicate | pierFunction |
P53816
|
FINISHED |
| Object | recreational fishing |
—
|
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: recreational fishing | Statement: [Ocean Beach, San Diego, pierFunction, recreational fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pierFunction Context triple: [Ocean Beach, San Diego, pierFunction, recreational fishing]
-
A.
hasPierFunction
chosen
Indicates that an entity serves the role or function of a pier, such as providing a structure that extends over water for access, docking, or related activities.
-
B.
pierOpened
Indicates that a pier has been officially opened or made available for use, typically at a specific time or event.
-
C.
specializesPierAIn
Indicates that one entity (typically a pier or terminal) is specifically designated or adapted for a particular type of use, service, or function.
-
D.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
E.
hasPiersOn
Indicates that one structure or location is supported or extended by piers that are physically situated on another structure or surface.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c0bac8081909e39d4e0aaf0f31d |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:26 p.m.