Triple
T11623189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurora, Ontario |
E276190
|
entity |
| Predicate | hasRegionalConnectivity |
P99274
|
FINISHED |
| Object | road network to 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: road network to Toronto | Statement: [Aurora, Ontario, hasRegionalConnectivity, road network to Toronto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalConnectivity Context triple: [Aurora, Ontario, hasRegionalConnectivity, road network to Toronto]
-
A.
hasRegionalServices
Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of regions.
-
B.
connectivityMode
Indicates how two or more entities are linked or able to communicate with each other, such as the type or method of connection used between them.
-
C.
connectsCountryOrRegion
chosen
Indicates that one entity establishes a connection, link, or association to a specific country or region.
-
D.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
E.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a122a3708190ab6513dad4c4fde7 |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.