Triple
T14307349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minto railway station |
E354731
|
entity |
| Predicate | hasOpalCardTopUp |
P113702
|
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: [Minto railway station, hasOpalCardTopUp, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpalCardTopUp Context triple: [Minto railway station, hasOpalCardTopUp, yes]
-
A.
hasMinimumBalanceForBusTramMetro
Indicates that an entity’s balance meets or exceeds the required minimum to use bus, tram, or metro services.
-
B.
hasMinimumBalanceForTrain
Indicates that an entity’s balance meets or exceeds the minimum required amount to use or board a train.
-
C.
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.
-
D.
canPayFor
Indicates that one entity has the ability or sufficient resources to cover the cost or expense of another entity.
-
E.
isPrepaid
Indicates that something has been paid for in advance before its use or delivery.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b156b0819083f2bd319deed1b6 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:12 a.m.