Triple
T38148089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn Avenue |
E952673
|
entity |
| Predicate | hasPublicTransitServiceType |
P31014
|
FINISHED |
| Object | bus rapid transit |
—
|
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: bus rapid transit | Statement: [Penn Avenue, hasPublicTransitServiceType, bus rapid transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicTransitServiceType Context triple: [Penn Avenue, hasPublicTransitServiceType, bus rapid transit]
-
A.
hasPublicTransitFunction
Indicates that something serves a role or provides a service related to public transportation operations or infrastructure.
-
B.
hasPublicTransitServiceLevel
Indicates the level or quality of public transit service provided to or available at a given location or entity.
-
C.
hasPublicTransitProvider
Indicates that a place or region is served by a specific public transit operating organization or agency.
-
D.
hasPublicTransitMode
chosen
Indicates that a location, route, or service is associated with or supports a specific mode of public transportation (e.g., bus, train, tram).
-
E.
hasPublicTransitCoverageType
Indicates the type or category of public transit service coverage associated with an entity.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:21 p.m.