Triple
T34477484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seymour, Indiana |
E885078
|
entity |
| Predicate | isHighwayHub |
P96996
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Seymour, Indiana, isHighwayHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighwayHub Context triple: [Seymour, Indiana, isHighwayHub, true]
-
A.
isTransportHubType
Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
-
B.
isRoadHub
chosen
Indicates that a location functions as a central node or major junction within a road network, connecting multiple routes.
-
C.
isMajorBusHub
Indicates that a location serves as a primary node in the bus network, with high connectivity and significant passenger or route volume.
-
D.
isGroundTransportHubFor
Indicates that a location functions as a central node or facility for organizing, coordinating, or serving ground-based transportation for another place or set of routes.
-
E.
majorHubServed
Indicates that a major transportation or logistical hub is served or connected by a particular route, service, or facility.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.