Triple
T11341402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadview station |
E268604
|
entity |
| Predicate | isInCitySector |
P39182
|
FINISHED |
| Object | east end of Toronto |
—
|
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: east end of Toronto | Statement: [Broadview station, isInCitySector, east end of Toronto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCitySector Context triple: [Broadview station, isInCitySector, east end of Toronto]
-
A.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
-
B.
isInMunicipality
Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
-
C.
isInArea
chosen
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
D.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
-
E.
isInAutonomousCity
Indicates that one entity is located within a city that has autonomous or self-governing administrative status.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea01c6c08190910a6ce8fb7e186d |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.