Triple
T28596676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Production Way–University station |
E723793
|
entity |
| Predicate | hasBusExchange |
P2423
|
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: [Production Way–University station, hasBusExchange, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusExchange Context triple: [Production Way–University station, hasBusExchange, yes]
-
A.
hasBusInterchange
chosen
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
B.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
C.
hasBusTerminalType
Indicates the specific category or type of bus terminal associated with an entity.
-
D.
hasBusStationStructure
Indicates that one entity serves as the physical structure or facility that functions as a bus station for another entity.
-
E.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 4:22 a.m.