Triple
T30223502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Lakefront |
E768411
|
entity |
| Predicate | isShorelineDistrictOf |
P119811
|
FINISHED |
| Object | Cleveland |
—
|
NE NERFINISHED |
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: Cleveland | Statement: [Cleveland Lakefront, isShorelineDistrictOf, Cleveland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShorelineDistrictOf Context triple: [Cleveland Lakefront, isShorelineDistrictOf, Cleveland]
-
A.
isCoastalDistrict
Indicates that a district is located along a coastline or has direct access to a sea or ocean.
-
B.
isWaterfrontDistrict
chosen
Indicates that a district is located directly along a body of water, such as a river, lake, or coastline.
-
C.
isBorderDistrict
Indicates that a district is located along and directly borders the boundary of a larger administrative region or country.
-
D.
hasShorelineCommunity
Indicates that a place or region includes or is associated with a community located along its shoreline.
-
E.
isCoastalCitySuburb
Indicates that a suburb is located within or adjacent to a city that lies on a coastline, functioning as a suburban area of that coastal city.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6801f64f08190b4061a0c030f9806 |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:35 p.m.