Triple
T24934937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne Free Tram Zone (CBD section) |
E623287
|
entity |
| Predicate | ticketInspectionRule |
P159395
|
FINISHED |
| Object | myki required if travelling beyond zone boundaries |
—
|
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: myki required if travelling beyond zone boundaries | Statement: [Melbourne Free Tram Zone (CBD section), ticketInspectionRule, myki required if travelling beyond zone boundaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketInspectionRule Context triple: [Melbourne Free Tram Zone (CBD section), ticketInspectionRule, myki required if travelling beyond zone boundaries]
-
A.
ticketInspectionRule
chosen
Indicates the rule or condition under which tickets are to be inspected or validated.
-
B.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
-
C.
ticketGatesType
Indicates the type or category of ticket gates associated with a given entity or location.
-
D.
ticketTypeAccepted
Indicates that a particular type of ticket is valid for use or accepted in a given context or by a given entity.
-
E.
ticketingScope
Indicates the range or domain within which ticketing actions (such as creation, assignment, or management of tickets) are valid or applicable.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 5:30 a.m.