Triple
T24897370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myki Zone 1 |
E623180
|
entity |
| Predicate | supportsFullFares |
P112377
|
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, supportsFullFares, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFullFares Context triple: [Myki Zone 1, supportsFullFares, true]
-
A.
usesSingleFareStructure
Indicates that the same fare rules and pricing structure are applied uniformly across all relevant services or routes.
-
B.
supportsTransitDiscounts
Indicates that an entity provides or enables discounted fares or pricing for public transit services.
-
C.
fareSystemFeature
chosen
Indicates that a fare system possesses or supports a particular feature, function, or characteristic related to how fares are calculated, managed, or used.
-
D.
hasFareControlIntegrationSince
Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
-
E.
farePolicySupport
Indicates that there is a policy in place governing fares (such as prices, discounts, or rules) that is recognized, enabled, or supported in the given context.
- 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_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 18, 2026, 5:26 a.m.