Triple
T26480250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bendigo railway station |
E664658
|
entity |
| Predicate | mykiZone |
P17300
|
FINISHED |
| Object | zone 13 |
—
|
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: zone 13 | Statement: [Bendigo railway station, mykiZone, zone 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mykiZone Context triple: [Bendigo railway station, mykiZone, zone 13]
-
A.
fareSystem
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
B.
hasOpalOrMykiGates
Indicates that a location or facility is equipped with Opal or Myki ticketing gates for access control or fare validation.
-
C.
fareSystemFeature
Indicates that a fare system possesses or supports a particular feature, function, or characteristic related to how fares are calculated, managed, or used.
-
D.
hasMykiTopUp
Indicates that an entity has performed or received a Myki card balance top-up transaction.
-
E.
publicTransportZone
chosen
Indicates that an entity is located within, associated with, or valid for a specific public transportation fare or service zone.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612fa3f4481908d1db59213f734d2 |
completed | May 2, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:26 a.m.