Triple
T11201320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wayne Route 23 Transit Center |
E265045
|
entity |
| Predicate | hasShelteredBusBays |
P19782
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Wayne Route 23 Transit Center, hasShelteredBusBays, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShelteredBusBays Context triple: [Wayne Route 23 Transit Center, hasShelteredBusBays, yes]
-
A.
hasBusBays
chosen
Indicates that a location or facility is equipped with one or more designated bus bays for buses to stop, load, or unload passengers.
-
B.
hasBusPlatforms
Indicates that a location or facility is equipped with one or more designated platforms for boarding or alighting from buses.
-
C.
hasShelteredEntrances
Indicates that an entity provides one or more entrances that are covered or protected from weather or external exposure.
-
D.
numberOfBays
Indicates the count of distinct bays associated with or contained within a given entity.
-
E.
hasBayPlatforms
Indicates that a station or terminal is equipped with bay platforms, where tracks end in a dead-end configuration and trains enter and exit from the same direction.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c36c188190bfa4d5f8e6cbbbea |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:29 p.m.