Triple
T24932314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upfield railway station |
E623219
|
entity |
| Predicate | hasOpalOrMykiValidators |
P108754
|
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: [Upfield railway station, hasOpalOrMykiValidators, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpalOrMykiValidators Context triple: [Upfield railway station, hasOpalOrMykiValidators, yes]
-
A.
hasOpalOrMykiGates
Indicates that a location or facility is equipped with Opal or Myki ticketing gates for access control or fare validation.
-
B.
hasOpalCardReaders
Indicates that an entity is equipped with or contains Opal card readers for processing Opal transit card transactions.
-
C.
hasSmartcardValidators
chosen
Indicates that an entity is equipped with or includes smartcard validation devices for reading or verifying smartcards.
-
D.
hasOysterCardReaders
Indicates that the subject is equipped with or contains Oyster card readers for validating or processing Oyster card transactions.
-
E.
hasMykiCardReaders
Indicates that an entity is equipped with or contains Myki card readers for processing Myki cards.
- 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_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:30 a.m.