Triple
T10726495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | False Creek |
E252959
|
entity |
| Predicate | wasIndustrialAreaUntil |
P95649
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [False Creek, wasIndustrialAreaUntil, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasIndustrialAreaUntil Context triple: [False Creek, wasIndustrialAreaUntil, mid-20th century]
-
A.
isIndustrialAreaOf
Indicates that a location functions primarily as an industrial zone or district associated with a specified area or jurisdiction.
-
B.
formerIndustrialTown
Indicates that a town previously had a significant industrial base or economy but no longer does.
-
C.
hasIndustrialAreaType
Indicates that an entity’s industrial area is classified as a specific type or category of industrial zone.
-
D.
partOfIndustrialRegion
Indicates that an entity is located within or belongs to a broader industrial region or industrially developed area.
-
E.
isIndustrialCommunity
Indicates that a community is primarily characterized by industrial activities, such as manufacturing, production, or related industrial operations.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70fc713f081909ba1d1b986c1fe5c |
completed | April 9, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:14 p.m.