Triple
T9768388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amtrak Palmetto |
E237055
|
entity |
| Predicate | ownerOfRouteSegments |
P90527
|
FINISHED |
| Object | uses tracks owned by Amtrak on the Northeast Corridor |
—
|
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: uses tracks owned by Amtrak on the Northeast Corridor | Statement: [Amtrak Palmetto, ownerOfRouteSegments, uses tracks owned by Amtrak on the Northeast Corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerOfRouteSegments Context triple: [Amtrak Palmetto, ownerOfRouteSegments, uses tracks owned by Amtrak on the Northeast Corridor]
-
A.
routeSegment
Indicates a specific portion of a larger route that directly connects two points or locations within that route.
-
B.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
C.
routeRole
Indicates the specific functional role or purpose that an entity has within a particular route or path.
-
D.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
E.
parentRoute
Indicates that one route serves as the direct hierarchical ancestor or container of another route within a routing structure.
- F. None of above. chosen
Provenance (4 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0a2da648190836916a45d2998d7 |
completed | April 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:25 p.m.