Triple
T29879042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklin, Ontario |
E758823
|
entity |
| Predicate | primaryDestinationForCommuters |
P61070
|
FINISHED |
| Object | Toronto |
E1525
|
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: Toronto | Statement: [Brooklin, Ontario, primaryDestinationForCommuters, Toronto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDestinationForCommuters Context triple: [Brooklin, Ontario, primaryDestinationForCommuters, Toronto]
-
A.
commuterDestination
chosen
Indicates that a location serves as the endpoint or target place to which a person regularly travels for commuting.
-
B.
commuterRoute
Indicates a route that is regularly used by people traveling between home and work or other routine daily destinations.
-
C.
commuterHubFor
Indicates a location that serves as a primary transit or gathering point for commuters traveling to or from another place.
-
D.
commuterServiceTo
Indicates a transportation service that regularly carries commuters to a specified destination.
-
E.
hasCommuterOrientation
Indicates that an entity is designed or intended primarily for use by commuters, emphasizing suitability for regular travel between home and work or study.
- F. None of above.
Provenance (4 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a01a819644c819094c58d083d525da0 |
completed | May 11, 2026, 9:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2721e1ce80819081aa7b21ff16f823 |
completed | June 8, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_6a01a5dfd628819083c032d8cfd2e726 |
completed | May 11, 2026, 9:48 a.m. |
Created at: April 29, 2026, 5:57 p.m.