Triple
T25207081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Officer railway station |
E631281
|
entity |
| Predicate | hasMyki |
P157247
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Officer railway station, hasMyki, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMyki Context triple: [Officer railway station, hasMyki, yes]
-
A.
hasMykiTopUp
Indicates that an entity has performed or received a Myki card balance top-up transaction.
-
B.
hasOpalCard
Indicates that an entity possesses or is assigned an Opal card.
-
C.
hasOpalOrMykiGates
chosen
Indicates that a location or facility is equipped with Opal or Myki ticketing gates for access control or fare validation.
-
D.
hasNearbyPass
Indicates that an entity has at least one pass (e.g., transit or access pass) available within a short or locally defined distance from it.
-
E.
hasTicket
Indicates that an entity possesses or holds a ticket, typically granting access, entry, or a right to a service or event.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 12:52 p.m.