Triple
T6082598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 390 |
E135558
|
entity |
| Predicate | couplingType |
P21783
|
FINISHED |
| Object | Dellner |
E119096
|
NE 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: Dellner | Statement: [British Rail Class 390, couplingType, Dellner]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dellner Context triple: [British Rail Class 390, couplingType, Dellner]
-
A.
Dellner
chosen
Dellner is a company specializing in railway coupling and connection systems used on modern passenger and freight trains worldwide.
-
B.
Diller
Diller is a surname most prominently associated with American media executive and businessman Barry Diller.
-
C.
Delson
Delson is a small suburban city located on Montreal's South Shore in the Montérégie region of Quebec, Canada.
-
D.
Durst
Durst is a surname most prominently associated with the New York real estate–developing Durst family, including figures such as Joseph Durst and his descendants.
-
E.
Edelmann
Edelmann is a surname of German origin borne by various individuals across fields such as music, sports, and academia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05786233c81909010a6c2f7e7dfda |
completed | March 22, 2026, 8:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11d57b5f481908d7df374837a486a |
completed | March 23, 2026, 11 a.m. |
Created at: March 22, 2026, 4:11 p.m.