Triple
T15252115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Wollongong railway station |
E364541
|
entity |
| Predicate | hasOpalTopUpMachine |
P117783
|
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 Wollongong railway station, hasOpalTopUpMachine, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpalTopUpMachine Context triple: [North Wollongong railway station, hasOpalTopUpMachine, yes]
-
A.
hasOpalCardTopUp
Indicates that an entity has performed or received a monetary top-up on an Opal card.
-
B.
hasOpalCardReaders
Indicates that an entity is equipped with or contains Opal card readers for processing Opal transit card transactions.
-
C.
hasVIPTerminal
Indicates that one entity possesses or provides access to a VIP (very important person) terminal associated with another entity.
-
D.
hasSelfServiceTicketMachines
Indicates that an entity is equipped with self-service ticket machines available for use.
-
E.
hasATMNetwork
Indicates that an entity operates, participates in, or is connected to a particular automated teller machine (ATM) network for financial transactions.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f728648190b2c86e4528542b65 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.