Triple
T28737251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lafarge Lake–Douglas station |
E730833
|
entity |
| Predicate | busExchange |
P2423
|
FINISHED |
| Object | on-street bus loop nearby |
—
|
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: on-street bus loop nearby | Statement: [Lafarge Lake–Douglas station, busExchange, on-street bus loop nearby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busExchange Context triple: [Lafarge Lake–Douglas station, busExchange, on-street bus loop nearby]
-
A.
interchangeStation
Indicates a station where passengers can transfer between different routes, lines, or modes of transportation.
-
B.
hasBusInterchange
chosen
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
C.
isMainBusStationFor
Indicates that one bus station serves as the primary or central station for a particular area, network, or service.
-
D.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
E.
transportationJunctionFor
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6576c4b60819088e0fd5fd275e7bf |
completed | May 2, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 6:01 a.m.