Triple
T16204392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finch Avenue West |
E393286
|
entity |
| Predicate | hasNeighbourhoodAlong |
P16140
|
FINISHED |
| Object | Humbermede |
E362835
|
NE 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: Humbermede | Statement: [Finch Avenue West, hasNeighbourhoodAlong, Humbermede]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Humbermede Context triple: [Finch Avenue West, hasNeighbourhoodAlong, Humbermede]
-
A.
Humbermede
chosen
Humbermede is a residential neighbourhood in the northwestern part of Toronto, Ontario, known for its diverse community and proximity to the Humber River.
-
B.
Hythe
Hythe is a small village in northwestern Alberta, Canada, situated west of the city of Grande Prairie.
-
C.
Hythe
Hythe is a historic coastal town in Kent, England, known as one of the original Cinque Ports that once played a key role in maritime defense and trade.
-
D.
Hildenborough
Hildenborough is a village in Kent, England, situated near Tonbridge and known for its commuter links to London and surrounding towns.
-
E.
Hellingly
Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2270d6e5c8190aee4bcca76cbe47c |
completed | April 17, 2026, 12:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffff14b0988190bb4128b2e02aee32 |
completed | May 10, 2026, 3:44 a.m. |
Created at: April 10, 2026, 5:03 a.m.