Triple
T1562821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodland Avenue |
E33364
|
entity |
| Predicate | hasPublicTransitRole |
P29465
|
FINISHED |
| Object | key trolley corridor |
—
|
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: key trolley corridor | Statement: [Woodland Avenue, hasPublicTransitRole, key trolley corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicTransitRole Context triple: [Woodland Avenue, hasPublicTransitRole, key trolley corridor]
-
A.
hasPublicTransitProvider
Indicates that a place or region is served by a specific public transit operating organization or agency.
-
B.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
-
C.
hasPublicTransitCoverageType
Indicates the type or category of public transit service coverage associated with an entity.
-
D.
hasPublicTransportStop
Indicates that a location or area contains or is served by a public transport stop, such as a bus, tram, or train stop.
-
E.
hasPublicTransitServiceLevel
Indicates the level or quality of public transit service provided to or available at a given location or entity.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a90fcb8ca48190a9ee50559ba73b22 |
completed | March 5, 2026, 5:08 a.m. |
Created at: March 4, 2026, 7:27 p.m.