Triple
T2526976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethan Allen Express |
E56057
|
entity |
| Predicate | routePassesThrough |
P34612
|
FINISHED |
| Object | upstate New York |
—
|
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: upstate New York | Statement: [Ethan Allen Express, routePassesThrough, upstate New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routePassesThrough Context triple: [Ethan Allen Express, routePassesThrough, upstate New York]
-
A.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
B.
passesThroughArea
chosen
Indicates that an entity moves or extends through the spatial region defined by another entity or area.
-
C.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
D.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
E.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd255f0d081908d20cfb812c4bfc1 |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.