Triple
T32270269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honest Ed’s site |
E824396
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical landmark area |
C17883
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical landmark area Context triple: [Honest Ed’s site, instanceOf, historical landmark area]
-
A.
historical district
A historical district is a geographically defined area recognized for its concentration of buildings, structures, and sites that collectively reflect significant cultural, architectural, or historical heritage.
-
B.
tourist attraction area
chosen
A tourist attraction area is a designated geographic location that offers notable natural, cultural, historical, or recreational features and supporting facilities that draw visitors for leisure, education, or entertainment.
-
C.
monument area
A monument area is a designated space that encompasses and protects a monument and its immediate surroundings, often including related structures, landscapes, and access features.
-
D.
architectural district
An architectural district is a geographically defined area characterized by a concentration of buildings and structures that share significant architectural styles, historical periods, or design features, often protected or managed for their cultural and aesthetic value.
-
E.
archaeological district
An archaeological district is a geographically defined area containing a significant concentration, linkage, or continuity of archaeological sites, features, or artifacts that collectively represent important historical or prehistorical activities or cultures.
- F. None of above.
Provenance (1 batch)
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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:42 a.m.