Triple
T27454989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Street (Toronto) |
E692563
|
entity |
| Predicate | hasNotableIntersectionArea |
P13379
|
FINISHED |
| Object | intersection with Wellesley Street |
—
|
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: intersection with Wellesley Street | Statement: [Church Street (Toronto), hasNotableIntersectionArea, intersection with Wellesley Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableIntersectionArea Context triple: [Church Street (Toronto), hasNotableIntersectionArea, intersection with Wellesley Street]
-
A.
hasNotableIntersection
chosen
Indicates that two entities intersect or cross at a point that is considered significant or noteworthy in some context.
-
B.
notableAreaWithin
Indicates that one area is a particularly significant or noteworthy part located inside another, larger area.
-
C.
hasIntermediateArea
Indicates that there exists an area or region that lies between or connects two other areas in the relationship.
-
D.
hasNotableSegment
Indicates that an entity includes or contains a specific segment, part, or portion that is considered notable or significant in some way.
-
E.
fieldIntersection
Indicates that two or more fields or domains share a common overlapping area or set of elements.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: April 27, 2026, 12:48 p.m.