Triple
T28803159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEPTA Route 98 |
E727297
|
entity |
| Predicate | isSuburbanRoute |
P169285
|
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: [SEPTA Route 98, isSuburbanRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSuburbanRoute Context triple: [SEPTA Route 98, isSuburbanRoute, true]
-
A.
isSuburbanRouteOf
Indicates that a given route functions as a suburban segment or service line belonging to, or operating as part of, a larger primary route or network.
-
B.
isSuburbanStreetOf
Indicates that one entity is a street located within or characteristic of the suburban area associated with another entity.
-
C.
isSuburbanArea
Indicates that a location is characterized as a suburban area, typically lying between urban and rural regions and exhibiting suburban development patterns.
-
D.
isSuburbanRidingOf
Indicates that one area or jurisdiction is a suburban electoral riding (district) associated with a larger urban center or region.
-
E.
isSuburbanDistrict
Indicates that a district is located in and characterized as part of the suburbs of a larger urban area.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f67de7792c81909b5e4e812d143624 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 28, 2026, 6:28 a.m.