Triple
T35892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dupont Circle |
E710
|
entity |
| Predicate | hasZoning |
P727
|
FINISHED |
| Object | mixed-use |
—
|
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: mixed-use | Statement: [Dupont Circle, hasZoning, mixed-use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZoning Context triple: [Dupont Circle, hasZoning, mixed-use]
-
A.
zoningCharacter
chosen
Indicates how the regulatory or functional nature of a geographic area is defined or classified in terms of land-use zoning.
-
B.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
C.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
D.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
E.
hasProtectedArea
Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24bb753f081909cd8b25cfb8e08af |
completed | Feb. 28, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69a24ab4a6908190b6f355415ffe7948 |
completed | Feb. 28, 2026, 1:53 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.