Triple
T24933354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willison railway station |
E623246
|
entity |
| Predicate | platform1Direction |
P158144
|
FINISHED |
| Object | towards Flinders Street |
—
|
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: towards Flinders Street | Statement: [Willison railway station, platform1Direction, towards Flinders Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platform1Direction Context triple: [Willison railway station, platform1Direction, towards Flinders Street]
-
A.
platform2Direction
Indicates the direction or orientation associated with a second platform in a given context.
-
B.
directedForPlatform
Indicates that something (such as content or a message) is specifically aimed at, tailored to, or intended for a particular platform.
-
C.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
-
D.
parallelServiceDirection
Indicates that two services operate in the same or corresponding direction, running parallel to each other in their routing or flow.
-
E.
lapDirection
Indicates the direction or orientation in which a lapping or overlapping action occurs between entities.
- 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_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 5:30 a.m.