Triple
T25884138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daylesford station |
E652132
|
entity |
| Predicate | primaryRailStopFor |
P27112
|
FINISHED |
| Object | Daylesford |
—
|
NE NERFINISHED |
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: Daylesford | Statement: [Daylesford station, primaryRailStopFor, Daylesford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRailStopFor Context triple: [Daylesford station, primaryRailStopFor, Daylesford]
-
A.
railNetworkStopOn
Indicates that a rail stop or station is located on and served by a particular rail network.
-
B.
railwayStationFor
chosen
Indicates a relationship where a railway station serves, is designated for, or primarily associated with a particular place, line, or service.
-
C.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
D.
primaryRailLinkFor
Indicates that one entity serves as the main or principal rail connection or route for another entity.
-
E.
railTerminusFor
Indicates that one location serves as the final or terminal rail station or endpoint for a specified rail line or service.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 22, 2026, 8:17 a.m.