Triple
T29292811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty Park (Clarksville, Tennessee) |
E742726
|
entity |
| Predicate | isWaterfrontPark |
P50459
|
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: [Liberty Park (Clarksville, Tennessee), isWaterfrontPark, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWaterfrontPark Context triple: [Liberty Park (Clarksville, Tennessee), isWaterfrontPark, true]
-
A.
hasWaterfrontPark
chosen
Indicates that a place or area includes or is associated with a park located directly along a body of water.
-
B.
isWaterfrontFacility
Indicates that a facility is located directly on or adjacent to a body of water, providing waterfront access or frontage.
-
C.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
-
D.
isWaterfrontFacilityType
Indicates that a facility is classified as a type specifically associated with or located on a waterfront.
-
E.
isWaterfrontThoroughfare
Indicates that a thoroughfare (such as a road, street, or path) is located directly along or adjacent to a body of water.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66541ad908190bfae0c3070a1f4c0 |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:03 p.m.