Triple
T24897372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myki Zone 1 |
E623180
|
entity |
| Predicate | supportsSeniorsFares |
P27915
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Myki Zone 1, supportsSeniorsFares, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSeniorsFares Context triple: [Myki Zone 1, supportsSeniorsFares, true]
-
A.
supportsTransitDiscounts
Indicates that an entity provides or enables discounted fares or pricing for public transit services.
-
B.
supportsAgeDiscounts
chosen
Indicates that the subject entity offers or honors special pricing or discounts based on a person's age.
-
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.
usesSingleFareStructure
Indicates that the same fare rules and pricing structure are applied uniformly across all relevant services or routes.
-
E.
usesFareMedium
Indicates that an entity employs a particular fare medium (such as a ticket, card, or pass) as the method of payment or validation for a trip or service.
- 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_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 5:26 a.m.