Triple
T21568824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Provincial sector |
E532230
|
entity |
| Predicate | didNotOperate |
P2509
|
FINISHED |
| Object | InterCity services |
—
|
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: InterCity services | Statement: [British Rail Provincial sector, didNotOperate, InterCity services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didNotOperate Context triple: [British Rail Provincial sector, didNotOperate, InterCity services]
-
A.
operatedWithout
Indicates that an action, process, or entity functioned or was carried out in the absence of a specified resource, condition, or participant.
-
B.
doesNotOperate
chosen
Indicates that an entity is not functioning, active, or performing its intended operation in relation to another entity or context.
-
C.
didNotHold
Indicates that an expected event, condition, or relationship failed to occur or be valid.
-
D.
didNotOverrule
Indicates that one entity, typically a higher authority or court, chose not to overturn, reverse, or invalidate the decision or ruling made by another entity.
-
E.
didNotBecome
Indicates that an expected or potential change of state, role, or condition between entities did not occur.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cad95c8190ab165ced6f242302 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.