Triple
T23035702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DMR |
E573587
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | DMR |
—
|
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: DMR | Statement: [DMR, hasAbbreviation, DMR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DMR Context triple: [DMR, hasAbbreviation, DMR]
-
A.
DMR
DMR is the commonly used abbreviation for the Dhaka Metro Rail, the rapid transit system serving Bangladesh’s capital city.
-
B.
DMR
DMR is a scientific instrument aboard the COBE satellite designed to measure tiny variations in the cosmic microwave background radiation across the sky.
-
C.
DMR
DMR is the station code for Deportivo 18 de Marzo, a Mexico City Metro station serving as an important transfer point in the network.
-
D.
DMR
DMR is the commonly used abbreviation for the Division of Mine Reclamation, a governmental body responsible for overseeing and regulating mine reclamation activities.
-
E.
DMR
DMR (Digital Mobile Radio) is an open digital radio standard used worldwide for professional mobile communications, offering efficient spectrum use, voice and data services, and interoperability between compliant equipment.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1850df7fc81909ee522d99d96af0d |
completed | April 29, 2026, 4:11 a.m. |
Created at: April 17, 2026, 3:53 p.m.