Triple
T23697486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goderich, Ontario |
E585487
|
entity |
| Predicate | streetPlanShape |
P47409
|
FINISHED |
| Object | octagonal town square |
—
|
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: octagonal town square | Statement: [Goderich, Ontario, streetPlanShape, octagonal town square]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetPlanShape Context triple: [Goderich, Ontario, streetPlanShape, octagonal town square]
-
A.
streetPlanBy
Indicates that a street or road layout was designed, organized, or planned by a particular agent or authority.
-
B.
hasStreetPlan
chosen
Indicates that an entity possesses or is associated with a specific layout or design plan for its streets.
-
C.
cityBlockShape
Indicates the geometric form or outline that defines the shape of a city block.
-
D.
urbanLayout
Indicates how the spatial arrangement, organization, and structure of buildings, streets, and public spaces relate to one another within an urban area.
-
E.
hasFloorPlanShape
Indicates that an entity has a specific geometric or structural configuration defining the shape of its floor plan.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b67f518481908d0f5b5e75b6ccd4 |
completed | April 29, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.