Triple
T26048653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 455 |
E647903
|
entity |
| Predicate | canWorkInMultipleWith |
P50884
|
FINISHED |
| Object | British Rail Class 456 |
—
|
NE NERFINISHED |
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: British Rail Class 456 | Statement: [British Rail Class 455, canWorkInMultipleWith, British Rail Class 456]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canWorkInMultipleWith Context triple: [British Rail Class 455, canWorkInMultipleWith, British Rail Class 456]
-
A.
canOperateInMultipleWith
chosen
Indicates that an entity is capable of functioning or being used concurrently within multiple instances, contexts, or configurations of another entity.
-
B.
canOperateInMultiple
Indicates that an entity is capable of functioning or being used across more than one context, environment, or mode.
-
C.
multipleWorkingType
Indicates that an entity is associated with more than one type of work or employment classification simultaneously.
-
D.
hasMultipleWorking
Indicates that an entity is associated with more than one working instance, role, or configuration simultaneously.
-
E.
multipleWorkingWith
Indicates that an entity is simultaneously collaborating or engaged in work with more than one other entity.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6065c200881908080a1069c63207b |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:10 a.m.