Triple
T34054096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton Harbour waterfront |
E873308
|
entity |
| Predicate | positionOnLakeOntario |
P156468
|
FINISHED |
| Object | western tip |
—
|
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: western tip | Statement: [Hamilton Harbour waterfront, positionOnLakeOntario, western tip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnLakeOntario Context triple: [Hamilton Harbour waterfront, positionOnLakeOntario, western tip]
-
A.
positionInGreatLakesChain
Indicates the relative location or ordering of an entity within the sequence of the Great Lakes.
-
B.
locatedOnGreatLake
chosen
Indicates that something is situated on the shore or directly adjacent to one of the Great Lakes.
-
C.
nearCityOnOntarioSide
Indicates that one entity is located close to a city that lies on the Ontario side of a border or region.
-
D.
isInLake
Indicates that one entity is located within the body of water defined as a lake.
-
E.
positionRelativeToNiagaraFalls
Indicates the spatial relationship of an entity’s location with respect to Niagara Falls, such as its direction, distance, or relative placement.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: May 1, 2026, 1:52 a.m.