Triple
T16196093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Brisbane railway station |
E393063
|
entity |
| Predicate | hasGoCardTopUp |
P122113
|
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: [South Brisbane railway station, hasGoCardTopUp, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoCardTopUp Context triple: [South Brisbane railway station, hasGoCardTopUp, yes]
-
A.
hasOpalCardTopUp
Indicates that an entity has performed or received a monetary top-up on an Opal card.
-
B.
hasCredit
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
-
C.
cardEligibility
Indicates whether an entity qualifies for or is allowed to receive a particular card under specified criteria.
-
D.
canPay
Indicates that one entity has the ability or authorization to make a payment to another entity or to settle a specified obligation.
-
E.
canPayFor
Indicates that one entity has the ability or sufficient resources to cover the cost or expense of another entity.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222d91130819080da4e2611612e27 |
completed | April 17, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.