Triple
T18963711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Worthing railway station |
E463975
|
entity |
| Predicate | accessBetweenPlatforms |
P78970
|
FINISHED |
| Object | level crossing |
—
|
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: level crossing | Statement: [East Worthing railway station, accessBetweenPlatforms, level crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessBetweenPlatforms Context triple: [East Worthing railway station, accessBetweenPlatforms, level crossing]
-
A.
accessToPlatforms
chosen
Indicates that one entity is able to use, reach, or interact with certain platforms provided or controlled by another entity.
-
B.
crossPlatformWith
Indicates that two systems, applications, or components are compatible with or operate across multiple platforms together.
-
C.
relatedToPlatform
Indicates that one entity has a general association or connection with a particular platform (such as a software, hardware, or service environment).
-
D.
relatedPlatformFunction
Indicates that one platform function is associated with, complements, or is otherwise functionally connected to another platform function.
-
E.
accessProtocol
Indicates the method or rules by which one entity is allowed to access or communicate with another entity or resource.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d420f481909aa22a0d22ac4af1 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon