Triple
T23851969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinatown, Ottawa |
E592193
|
entity |
| Predicate | gatewayLocation |
P154186
|
FINISHED |
| Object | Somerset Street West at Cambridge 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: Somerset Street West at Cambridge Street | Statement: [Chinatown, Ottawa, gatewayLocation, Somerset Street West at Cambridge Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gatewayLocation Context triple: [Chinatown, Ottawa, gatewayLocation, Somerset Street West at Cambridge Street]
-
A.
connectionLocation
Indicates the place or spatial context where a connection between entities occurs or is established.
-
B.
regionGatewayTo
Indicates that one region functions as an entry point or primary access route to another region.
-
C.
portalLocation
Indicates that a portal is situated at or associated with a specific location.
-
D.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
-
E.
tunnelLocation
Indicates that one entity is the location or site where a tunnel is situated or passes through in relation to another 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c987c3208190bf3f210d12106927 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:11 p.m.