Triple
T30980916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiburon as a railroad terminus |
E789369
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic transportation hub |
C41946
|
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 hub Context triple: [Tiburon as a railroad terminus, instanceOf, historic transportation hub]
-
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.
historic passageway
A historic passageway is an architectural corridor, alley, or tunnel that has been preserved or recognized for its cultural, historical, or architectural significance as a route connecting different spaces or areas.
-
C.
historic railroad town
chosen
A historic railroad town is a community whose growth, economy, and cultural identity were fundamentally shaped by its role as a hub or stop along early railway lines.
-
D.
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.
-
E.
historic portage route
A historic portage route is a traditional overland path used to carry watercraft and goods between navigable waterways, often significant for its cultural, economic, and transportation history.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:55 p.m.