Triple
T15404200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South End business district |
E368406
|
entity |
| Predicate | zoningDesignation |
P9954
|
FINISHED |
| Object | commercial |
—
|
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: commercial | Statement: [South End business district, zoningDesignation, commercial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoningDesignation Context triple: [South End business district, zoningDesignation, commercial]
-
A.
cityPlanningDesignation
chosen
Indicates how an area is officially classified or designated within urban or municipal planning (e.g., residential, commercial, industrial).
-
B.
environmentDesignation
Indicates that an entity is assigned a specific environmental classification or status within a given context.
-
C.
leaseDesignation
Indicates that an entity is formally assigned or designated as the subject or holder of a particular lease.
-
D.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
-
E.
zoningCharacter
Indicates how the regulatory or functional nature of a geographic area is defined or classified in terms of land-use zoning.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8fde64819082ec0c68df305561 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.