Triple
T27250368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myki Zone 16 |
E687467
|
entity |
| Predicate | farePolicyJurisdiction |
P143953
|
FINISHED |
| Object | Victorian Government |
—
|
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: Victorian Government | Statement: [Myki Zone 16, farePolicyJurisdiction, Victorian Government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farePolicyJurisdiction Context triple: [Myki Zone 16, farePolicyJurisdiction, Victorian Government]
-
A.
farePolicyAuthority
Indicates that an authority or organization is responsible for defining, regulating, or overseeing the fare policy applied to a transportation service or route.
-
B.
farePolicySource
chosen
Indicates the origin or authority from which a particular fare policy is derived or defined.
-
C.
farePolicyRelatedTo
Indicates a relationship where a fare policy is associated with, applies to, or governs a particular entity, context, or service.
-
D.
farePolicyAspect
Indicates a specific rule, condition, or feature that characterizes some aspect of a fare policy.
-
E.
farePolicyType
Indicates the type or category of fare policy that governs how prices, rules, or conditions are applied.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626b4e84c8190bab9109a20ce29f6 |
completed | May 2, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 10:44 a.m.