Triple
T24932781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craigieburn railway station |
E623232
|
entity |
| Predicate | hasPlatform1Usage |
P158749
|
FINISHED |
| Object | services to Flinders Street and city loop |
—
|
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: services to Flinders Street and city loop | Statement: [Craigieburn railway station, hasPlatform1Usage, services to Flinders Street and city loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlatform1Usage Context triple: [Craigieburn railway station, hasPlatform1Usage, services to Flinders Street and city loop]
-
A.
hasPrimaryPlatform
Indicates that one entity is designated as the main or principal platform associated with another entity.
-
B.
usedByPlatform
Indicates that something (such as a tool, component, or resource) is utilized or employed by a particular platform.
-
C.
usedOnPlatformType
Indicates that something is utilized or operates on a specific type of platform.
-
D.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
E.
hasPlatformNumber
Indicates that a location or service is associated with a specific platform identified by a platform number.
- 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_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 18, 2026, 5:30 a.m.