Triple
T12813677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto street network |
E306335
|
entity |
| Predicate | organizedAlong |
P4786
|
FINISHED |
| Object | grid pattern |
—
|
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: grid pattern | Statement: [Toronto street network, organizedAlong, grid pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedAlong Context triple: [Toronto street network, organizedAlong, grid pattern]
-
A.
organizedAs
chosen
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
B.
organizedAround
Indicates that something is structured, arranged, or centered with respect to a particular focus, principle, or organizing element.
-
C.
organizedUnder
Indicates that one entity is administratively or structurally placed within, and governed or managed by, another entity.
-
D.
organizedFrom
Indicates that something has been arranged, structured, or formed starting from a specified source or initial set of elements.
-
E.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9adcf08190a12801adcc613477 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.