Triple
T13709020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Episcopal Diocese of Western Michigan |
E328720
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | EDWM |
E328720
|
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: EDWM | Statement: [Episcopal Diocese of Western Michigan, abbreviation, EDWM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EDWM Context triple: [Episcopal Diocese of Western Michigan, abbreviation, EDWM]
-
A.
EDWM
chosen
EDWM is the commonly used abbreviation for the Episcopal Diocese of Western Michigan, a regional jurisdiction of the Episcopal Church in the United States.
-
B.
EDW
EDW is the National Rail station code for East Dulwich railway station in London, England.
-
C.
EDW
EDW is the ICAO airline designator assigned to Edelweiss Air, a Swiss leisure carrier based in Zurich.
-
D.
EDNM
EDNM is the commonly used abbreviation for the Episcopal Diocese of Northern Michigan, a regional jurisdiction of the Episcopal Church in the United States.
-
E.
EDOM
EDOM is the commonly used abbreviation for the Episcopal Diocese of Maine, a regional jurisdiction of the Episcopal Church in the United States.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43949e6c8190ae5e4fa119cde33a |
completed | April 13, 2026, 7:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7945d6b9481909cc627883dd24a85 |
completed | May 3, 2026, 6:30 p.m. |
Created at: April 9, 2026, 9:54 p.m.