Triple
T30902027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greyhound Bus Station (Blytheville, Arkansas) |
E787195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic transportation building |
C48269
|
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 transportation building Context triple: [Greyhound Bus Station (Blytheville, Arkansas), instanceOf, historic transportation building]
-
A.
historic transportation system
A historic transportation system is an organized network of vehicles, routes, and infrastructure from a past era that once facilitated the movement of people or goods and is now preserved, studied, or remembered for its cultural, technological, or historical significance.
-
B.
historicBuilding
chosen
A historicBuilding is a structure of significant age recognized for its cultural, architectural, or historical importance and often preserved or protected for future generations.
-
C.
historic infrastructure
Historic infrastructure comprises long-standing physical structures and systems—such as bridges, roads, canals, and railways—that were built in the past and continue to embody cultural, technological, and architectural significance.
-
D.
historic commercial building
A historic commercial building is a long-standing structure originally designed and used for business or trade that holds architectural, cultural, or historical significance.
-
E.
historic post station
A historic post station is a former officially designated stopping place along old travel or trade routes where travelers, mail, and goods were exchanged, often providing lodging, stables, and other services.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:50 p.m.