Triple
T25776048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West End of Toronto |
E649151
|
entity |
| Predicate | containsWaterfront |
P19053
|
FINISHED |
| Object | Lake Ontario shoreline |
—
|
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: Lake Ontario shoreline | Statement: [West End of Toronto, containsWaterfront, Lake Ontario shoreline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsWaterfront Context triple: [West End of Toronto, containsWaterfront, Lake Ontario shoreline]
-
A.
hasWaterfrontType
Indicates that an entity is associated with a specific type or category of waterfront (e.g., oceanfront, lakefront, riverfront).
-
B.
hasWaterfrontArea
chosen
Indicates that an entity possesses or includes an area directly adjacent to or bordering a body of water.
-
C.
hasWaterfrontView
Indicates that a property or location offers a direct view of a body of water from its premises.
-
D.
locatedInWaterfrontArea
Indicates that something is situated within a designated waterfront area adjacent to a body of water.
-
E.
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.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 22, 2026, 5:34 a.m.