Triple
T13974081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEPTA Bus Route XH |
E336138
|
entity |
| Predicate | servedNeighborhoodType |
P68386
|
FINISHED |
| Object | urban neighborhoods |
—
|
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: urban neighborhoods | Statement: [SEPTA Bus Route XH, servedNeighborhoodType, urban neighborhoods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedNeighborhoodType Context triple: [SEPTA Bus Route XH, servedNeighborhoodType, urban neighborhoods]
-
A.
notableNeighborhoodType
Indicates that a neighborhood is notably characterized by, or strongly associated with, a particular type or category (e.g., residential, commercial, historic).
-
B.
areaServedType
chosen
Indicates the type or category of area that is served by an entity or service.
-
C.
cityServedType
Indicates the type or category of city that is served by a given entity (such as a facility, service, or infrastructure).
-
D.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
E.
servedNearbyEstates
Indicates that an entity provided services or assistance to estates located in its immediate geographic vicinity.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e8fd6d48190a157eae8df3a2f3a |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.