Triple
T24412628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilkeston railway station |
E615492
|
entity |
| Predicate | hasOperatorCategory |
P82601
|
FINISHED |
| Object | National Rail station |
—
|
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: National Rail station | Statement: [Ilkeston railway station, hasOperatorCategory, National Rail station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperatorCategory Context triple: [Ilkeston railway station, hasOperatorCategory, National Rail station]
-
A.
hasOperatorSection
Indicates that something includes or is associated with a specific section intended for operators or operational use.
-
B.
isOperatorOn
Indicates that one entity serves as an operator responsible for operating, controlling, or managing another entity (such as a system, machine, or process).
-
C.
hasSupportCategory
Indicates that an entity is associated with a particular type or category of support it receives or provides.
-
D.
hasCategorySystem
chosen
Indicates that an entity is associated with or organized according to a particular categorization system.
-
E.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2958241e48190ae33297c5c5c0e59 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:11 a.m.