Triple
T18253885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Progress Rail |
E437170
|
entity |
| Predicate | brand |
P1500
|
FINISHED |
| Object | EMD |
—
|
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: EMD | Statement: [Progress Rail, brand, EMD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EMD Context triple: [Progress Rail, brand, EMD]
-
A.
EMD
EMD is the commonly used abbreviation for the Engineering Management Division, a professional group focused on the practice and advancement of engineering management.
-
B.
EMD
EMD is the vehicle registration code assigned to the German town of Emden.
-
C.
EMD
chosen
EMD is a major American manufacturer of diesel-electric locomotives and related railway equipment, historically known for its influential role in the development of modern rail transportation.
-
D.
EMD
EMD is an industry-standard electronic document used in air travel to record and manage ancillary services and fees such as baggage, seat selection, and other optional charges.
-
E.
EMD
EMD is the National Rail station code for East Midlands Parkway railway station in England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd82f81c81909ad4455954bd8caa |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 10:33 a.m.