Triple
T25207318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clayton railway station |
E631287
|
entity |
| Predicate | gradeSeparationType |
P90529
|
FINISHED |
| Object | rail over road |
—
|
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: rail over road | Statement: [Clayton railway station, gradeSeparationType, rail over road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gradeSeparationType Context triple: [Clayton railway station, gradeSeparationType, rail over road]
-
A.
gradeSeparationProject
Indicates a project whose purpose is to separate different transportation routes or levels (such as roads and railways) so they no longer intersect at the same grade.
-
B.
typeOfSeparation
chosen
Indicates the specific manner or category of separation that exists or occurred between entities.
-
C.
definedSeparationFrom
Indicates a formally specified distinction or boundary established between one entity and another.
-
D.
providesSeparationFor
Indicates that one entity serves to divide, isolate, or keep another entity apart from something else.
-
E.
gradeSeparated
Indicates that two intersecting transportation routes are physically separated by different elevation levels so they do not cross at the same grade.
- 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_69f474bce13c8190bcdd22cdd70490b5 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 12:52 p.m.