Triple
T31876519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Street area |
E813758
|
entity |
| Predicate | streetPatternFocusedOn |
P173463
|
FINISHED |
| Object | Queen Street |
—
|
NE NERFINISHED |
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: Queen Street | Statement: [Queen Street area, streetPatternFocusedOn, Queen Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetPatternFocusedOn Context triple: [Queen Street area, streetPatternFocusedOn, Queen Street]
-
A.
streetPatternChangedBy
Indicates that a change in the configuration, layout, or organization of a street network was caused or implemented by a specific agent or process.
-
B.
streetFunction
Indicates the functional role or primary use of a street within a transportation or urban context (e.g., residential, arterial, commercial access).
-
C.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other entity.
-
D.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
E.
streetPatternNamedFor
Indicates that a street pattern or layout is named in honor of, or derived from, a particular entity.
- F. None of above. chosen
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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 30, 2026, 11:55 p.m.