Triple
T4043826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z 8800 EMU |
E84014
|
entity |
| Predicate | multipleUnitType |
P28425
|
FINISHED |
| Object | EMU |
E284702
|
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: EMU | Statement: [Z 8800 EMU, multipleUnitType, EMU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EMU Context triple: [Z 8800 EMU, multipleUnitType, EMU]
-
A.
EMU
EMU is the European Union’s framework for coordinating economic policy and managing the single currency, the euro, among participating member states.
-
B.
EMU
chosen
EMU (Electric Multiple Unit) is a self-propelled train consisting of multiple carriages powered by electricity, commonly used for passenger rail services.
-
C.
EMD
EMD is the commonly used abbreviation for the Engineering Management Division, a professional group focused on the practice and advancement of engineering management.
-
D.
EMD
EMD is the vehicle registration code assigned to the German town of Emden.
-
E.
EA
EA is the commonly used abbreviation for the Environment Agency, the public body responsible for environmental protection and regulation in England.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb5d759c8190b61fbbe94ffe2bf7 |
completed | March 9, 2026, 4:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5564fb54c81909f40ca1d6f1e521e |
completed | March 14, 2026, 12:36 p.m. |
Created at: March 9, 2026, 3:37 p.m.