Triple
T22889798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenferrie railway station |
E567704
|
entity |
| Predicate | hasFareZoneHistory |
P19784
|
FINISHED |
| Object | formerly Metcard Zone 1 |
—
|
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: formerly Metcard Zone 1 | Statement: [Glenferrie railway station, hasFareZoneHistory, formerly Metcard Zone 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFareZoneHistory Context triple: [Glenferrie railway station, hasFareZoneHistory, formerly Metcard Zone 1]
-
A.
hasFormerFareZone
chosen
Indicates that an entity was previously assigned to a particular fare zone, but is no longer in that fare zone.
-
B.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
C.
fareZoneSince
Indicates the date or time from which a particular fare zone assignment has been in effect for an entity.
-
D.
hasFareZoneSystem
Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
-
E.
hasFarePaidArea
Indicates that an entity includes or is associated with a zone where access is restricted to users who have paid a fare.
- 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_69e2458a92ec81908fc1cd5f6407d2ab |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17fc479d48190a8218eceaebd6cc8 |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:40 p.m.