Triple
T13498406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACS-64 |
E320818
|
entity |
| Predicate | operatorFleetNumberRangeAmtrak |
P110663
|
FINISHED |
| Object | 600–670 |
—
|
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: 600–670 | Statement: [ACS-64, operatorFleetNumberRangeAmtrak, 600–670]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorFleetNumberRangeAmtrak Context triple: [ACS-64, operatorFleetNumberRangeAmtrak, 600–670]
-
A.
railFranchise
Indicates a contractual relationship in which a company is granted the right to operate rail services or manage rail infrastructure within a specified area or route.
-
B.
operatedBetweenStations
Indicates that an operation, such as a service or route, took place connecting or running between two specified stations.
-
C.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
D.
railroadServiceScope
Indicates the extent or coverage area within which a railroad service operates or is applicable.
-
E.
operatesCommuterServiceBetween
Indicates that an entity runs a commuter transportation service connecting two specified locations.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4fab688190bdc746985b0c7338 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:43 p.m.