Triple
T19480766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buttonwood tree on Wall Street |
E487374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic meeting place |
C21700
|
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: historic meeting place Context triple: [Buttonwood tree on Wall Street, instanceOf, historic meeting place]
-
A.
historic civic space
chosen
A historic civic space is a publicly accessible area of enduring cultural, political, or social significance where communities have traditionally gathered for collective activities, events, and civic life.
-
B.
historic meetinghouse
A historic meetinghouse is a preserved building that historically served as a central gathering place for community, religious, or civic activities.
-
C.
historic intersection
A historic intersection is a crossroads or junction that has significant cultural, social, or political importance due to notable events, architecture, or long-standing community activity that occurred or developed there.
-
D.
historic city square
A historic city square is a central public open space in a town or city, typically surrounded by significant buildings and monuments, that has served as a focal point for social, political, and commercial activities over time.
-
E.
historic urban center
A historic urban center is a densely built core area of a city characterized by its preserved architectural heritage, traditional street patterns, and long-standing cultural, social, and economic significance.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:39 p.m.