Triple
T27397990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Street (Alexandria, Virginia) |
E691743
|
entity |
| Predicate | hasSectionWithZoning |
P85325
|
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: [Duke Street (Alexandria, Virginia), hasSectionWithZoning, commercial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSectionWithZoning Context triple: [Duke Street (Alexandria, Virginia), hasSectionWithZoning, commercial]
-
A.
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.
-
B.
hasZoneStructure
Indicates that an entity possesses a defined internal division into zones or regions, each forming part of its overall structure.
-
C.
hasSectionWith
chosen
Indicates that an entity contains or includes a specific section that satisfies certain conditions or characteristics.
-
D.
hasSectionIn
Indicates that one entity contains or includes another entity as a section or subdivision within it.
-
E.
hasSectionAlong
Indicates that one entity includes or runs along a specific segment or portion of another entity.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 27, 2026, 12:28 p.m.