Triple
T19184954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonial Beach Municipal Pier |
E469677
|
entity |
| Predicate | isWaterfrontLandmark |
P120233
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Colonial Beach Municipal Pier, isWaterfrontLandmark, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWaterfrontLandmark Context triple: [Colonial Beach Municipal Pier, isWaterfrontLandmark, true]
-
A.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
-
B.
isBoatingLandmark
chosen
Indicates that a location serves as a notable reference point or feature specifically used for boating navigation or activities.
-
C.
isWaterfrontThoroughfare
Indicates that a thoroughfare (such as a road, street, or path) is located directly along or adjacent to a body of water.
-
D.
isCentralWaterfrontOf
Indicates that one location serves as the primary waterfront area or main waterside district of another place.
-
E.
isWaterfrontFacilityType
Indicates that a facility is classified as a type specifically associated with or located on a waterfront.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f6202b3881908b34ec4921fb90ca |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.