Triple
T24898358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cranbourne railway station |
E623204
|
entity |
| Predicate | hasTicketingZoneSystem |
P72429
|
FINISHED |
| Object | Myki zones |
—
|
NE NERFINISHED |
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: Myki zones | Statement: [Cranbourne railway station, hasTicketingZoneSystem, Myki zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketingZoneSystem Context triple: [Cranbourne railway station, hasTicketingZoneSystem, Myki zones]
-
A.
ticketZoneSystem
Indicates that there is a specific fare or access zoning system governing how tickets are defined, priced, or validated within a transport or event context.
-
B.
hasFareZoneSystem
chosen
Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
-
C.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
D.
ticketingZoneType
Indicates the type or category of ticketing zone that applies within a given area or context.
-
E.
hasFareZoneFeature
Indicates that an entity is associated with a specific fare zone or fare-related area designation.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 5:26 a.m.