Triple
T11201327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wayne Route 23 Transit Center |
E265045
|
entity |
| Predicate | hasBusLoops |
P48776
|
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, hasBusLoops, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusLoops Context triple: [Wayne Route 23 Transit Center, hasBusLoops, yes]
-
A.
hasBusLoop
chosen
Indicates that a location or facility includes a designated looped roadway or area specifically for bus circulation, stopping, or turning.
-
B.
hasBusArchitecture
Indicates that one entity uses, implements, or is characterized by a particular bus architecture in its design or operation.
-
C.
hasBusBays
Indicates that a location or facility is equipped with one or more designated bus bays for buses to stop, load, or unload passengers.
-
D.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
E.
hasStreetcarLoop
Indicates that a location or facility includes a dedicated looped track or route specifically for streetcars to turn around or circulate.
- 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.