Triple
T22387812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 323 |
E553438
|
entity |
| Predicate | operatorUse |
P147459
|
FINISHED |
| Object | stopping 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: stopping services | Statement: [British Rail Class 323, operatorUse, stopping services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorUse Context triple: [British Rail Class 323, operatorUse, stopping services]
-
A.
operator
Indicates that one entity functions as the operator (controller or handler) of another entity, such as a system, device, or process.
-
B.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
C.
usedByOperator
Indicates that something is utilized or operated by a particular operator or operating entity.
-
D.
operatorVariant
Indicates a relationship where one operator is an alternative or modified form of another, typically differing in implementation, configuration, or usage while serving a related function.
-
E.
exportUse
Indicates that something is used, intended, or suitable for export from one place or market to another.
- F. None of above. chosen
Provenance (4 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15857fb588190b8180963aedd69c0 |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e73597b51c8190aeff27f4779b82f3 |
completed | April 21, 2026, 8:30 a.m. |
Created at: April 16, 2026, 8:45 p.m.