Triple
T24898739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Brighton railway station |
E623214
|
entity |
| Predicate | hasMykiValidator |
P123567
|
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: [North Brighton railway station, hasMykiValidator, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMykiValidator Context triple: [North Brighton railway station, hasMykiValidator, yes]
-
A.
hasMykiTopUp
Indicates that an entity has performed or received a Myki card balance top-up transaction.
-
B.
hasOpalOrMykiGates
Indicates that a location or facility is equipped with Opal or Myki ticketing gates for access control or fare validation.
-
C.
hasOpalCard
Indicates that an entity possesses or is assigned an Opal card.
-
D.
hasMykiCardReaders
chosen
Indicates that an entity is equipped with or contains Myki card readers for processing Myki cards.
-
E.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
- 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_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 5:26 a.m.