Triple
T24932435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewell railway station |
E623222
|
entity |
| Predicate | hasOpalCard |
P157873
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Jewell railway station, hasOpalCard, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpalCard Context triple: [Jewell railway station, hasOpalCard, no]
-
A.
hasOpalCardTopUp
Indicates that an entity has performed or received a monetary top-up on an Opal card.
-
B.
hasOpalOrMykiGates
Indicates that a location or facility is equipped with Opal or Myki ticketing gates for access control or fare validation.
-
C.
hasOpalCardReaders
Indicates that an entity is equipped with or contains Opal card readers for processing Opal transit card transactions.
-
D.
hasExpressPassAccess
Indicates that an entity is granted special expedited or priority access, typically bypassing standard queues or procedures.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 5:30 a.m.