Triple
T5382234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Outlet Shops of Grand River |
E113112
|
entity |
| Predicate | isCommercialProperty |
P23616
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Outlet Shops of Grand River, isCommercialProperty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommercialProperty Context triple: [The Outlet Shops of Grand River, isCommercialProperty, true]
-
A.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
B.
nonResidential
Indicates that something is not intended or used for residential or living purposes.
-
C.
hasCommercialFunction
chosen
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
D.
commercialArea
Indicates that the location or region is designated primarily for commercial activities such as businesses, shops, or services.
-
E.
isCommercialPort
Indicates that a location functions as a port used for commercial or trade-related maritime activities.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86d163f88190939638d44fcb24a7 |
completed | March 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.