Triple
T27250360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myki Zone 16 |
E687467
|
entity |
| Predicate | transportRegionType |
P128584
|
FINISHED |
| Object | outer regional |
—
|
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: outer regional | Statement: [Myki Zone 16, transportRegionType, outer regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportRegionType Context triple: [Myki Zone 16, transportRegionType, outer regional]
-
A.
transportationRegion
Indicates that one entity serves as, or is associated with, a geographic region relevant to the transportation activities or coverage of another entity.
-
B.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
C.
regionalType
chosen
Indicates the classification of a region according to its designated type or category within a broader geographic or administrative system.
-
D.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
E.
typicalRegionType
Indicates that a region is of a characteristic or commonly occurring type for a given context or entity.
- 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_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 27, 2026, 10:44 a.m.