Triple
T13498407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACS-64 |
E320818
|
entity |
| Predicate | operatorFleetNumberRangeSEPTA |
P110664
|
FINISHED |
| Object | 901–915 |
—
|
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: 901–915 | Statement: [ACS-64, operatorFleetNumberRangeSEPTA, 901–915]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorFleetNumberRangeSEPTA Context triple: [ACS-64, operatorFleetNumberRangeSEPTA, 901–915]
-
A.
acquiredBySEPTA
Indicates that an entity has been purchased or taken over by SEPTA (the Southeastern Pennsylvania Transportation Authority).
-
B.
RVNumberRange
Indicates that a recreational vehicle’s number or identifier falls within a specified numeric range.
-
C.
operatesBetween
Indicates a relationship where an action, process, or influence functions or takes effect in the space, interval, or context separating two entities.
-
D.
operatesCommuterServiceBetween
Indicates that an entity runs a commuter transportation service connecting two specified locations.
-
E.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
- 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.