Triple
T25316319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burlingame, California |
E634753
|
entity |
| Predicate | hasWaterfrontTrail |
P76775
|
FINISHED |
| Object | Bayfront Park trail |
—
|
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: Bayfront Park trail | Statement: [Burlingame, California, hasWaterfrontTrail, Bayfront Park trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterfrontTrail Context triple: [Burlingame, California, hasWaterfrontTrail, Bayfront Park trail]
-
A.
hasShorelineTrail
chosen
Indicates that a location or body of water is connected to or bordered by a trail that runs along its shoreline.
-
B.
hasWaterfrontPark
Indicates that a place or area includes or is associated with a park located directly along a body of water.
-
C.
hasWaterfrontType
Indicates that an entity is associated with a specific type or category of waterfront (e.g., oceanfront, lakefront, riverfront).
-
D.
hasWaterfrontAccessTo
Indicates that one entity is directly adjacent to and can physically access a particular body of water, such as a lake, river, or ocean.
-
E.
hasWaterfrontUse
Indicates that an entity is used, designated, or suitable for activities or purposes directly related to a waterfront or shoreline 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:28 p.m.