Triple
T9172520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fenway neighborhood |
E220113
|
entity |
| Predicate | hasTypeOfZoning |
P727
|
FINISHED |
| Object | residential |
—
|
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: residential | Statement: [Fenway neighborhood, hasTypeOfZoning, residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfZoning Context triple: [Fenway neighborhood, hasTypeOfZoning, residential]
-
A.
hasIndustrialZoning
Indicates that a given area or property is designated for industrial use under zoning regulations.
-
B.
hasZoningPolicy
Indicates that a governing body or authority has established or adopted a specific zoning policy that regulates land use or development within its jurisdiction.
-
C.
hasZoningApproach
Indicates the type or method of zoning policy or strategy that is applied to or associated with an entity.
-
D.
zoningAuthority
Indicates that an entity has official power or jurisdiction to regulate land use and development within a specified area.
-
E.
zoningCharacter
chosen
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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbf9fe79c819082f335c2fdd1c7d3 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.