Triple
T24897367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myki Zone 1 |
E623180
|
entity |
| Predicate | fareSystemReplaced |
P118934
|
FINISHED |
| Object | Metcard |
—
|
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: Metcard | Statement: [Myki Zone 1, fareSystemReplaced, Metcard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareSystemReplaced Context triple: [Myki Zone 1, fareSystemReplaced, Metcard]
-
A.
fareSystemChange
Indicates a change in the rules, structure, or method by which fares are calculated, collected, or applied.
-
B.
fareSystemPreviously
chosen
Indicates that a particular fare system existed or was in use at an earlier time relative to another fare system or time period.
-
C.
fareSystem
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
D.
fareSystemFeature
Indicates that a fare system possesses or supports a particular feature, function, or characteristic related to how fares are calculated, managed, or used.
-
E.
fareSystemUse
Indicates the use or application of a particular fare system for travel, ticketing, or pricing.
- 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_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:26 a.m.