Triple
T14070070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEPTA Bus Route 57 |
E338581
|
entity |
| Predicate | primaryStreets |
P99920
|
FINISHED |
| Object | 3rd Street |
—
|
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: 3rd Street | Statement: [SEPTA Bus Route 57, primaryStreets, 3rd Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStreets Context triple: [SEPTA Bus Route 57, primaryStreets, 3rd Street]
-
A.
primaryStreetAlignment
Indicates that two or more primary streets share the same or a specified relative directional orientation or alignment.
-
B.
isPrimarySurfaceStreetIn
chosen
Indicates that a street serves as a main or primary surface-level roadway within a specified area or jurisdiction.
-
C.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
D.
betweenStreets
Indicates that one location is situated between two specified streets, typically along a road segment bounded by those streets.
-
E.
hasMainResidentialStreet
Indicates that an entity is associated with or served by a specific primary street used predominantly for residential purposes.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568d0404819087e0fe37c72162cb |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.