Triple
T25207285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springvale railway station |
E631286
|
entity |
| Predicate | hasOpalSystem |
P117783
|
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: [Springvale railway station, hasOpalSystem, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpalSystem Context triple: [Springvale railway station, hasOpalSystem, no]
-
A.
hasOpalEquivalent
Indicates that one entity corresponds to or is equivalent to another entity within the context of the Opal system or representation.
-
B.
hasOpalType
Indicates that an entity is associated with or classified by a specific type of opal.
-
C.
hasBaseSystem
Indicates that one entity is founded upon, derived from, or primarily operates using another entity as its underlying system or framework.
-
D.
hasOpalTopUpMachine
chosen
Indicates that a location or facility is equipped with an Opal card top-up machine for adding credit or purchasing travel value.
-
E.
operatedOnSystem
Indicates that an entity has performed operations or actions upon a particular system, affecting its state or behavior.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 12:52 p.m.