Triple
T6696281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udmurt language |
E152758
|
entity |
| Predicate | ISO639-1Code |
P208
|
FINISHED |
| Object | udm |
E523099
|
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: udm | Statement: [Udmurt language, ISO639-1Code, udm]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: udm Context triple: [Udmurt language, ISO639-1Code, udm]
-
A.
UDM
chosen
UDM (Unified Data Management) is a 5G core network function responsible for managing subscriber data, authentication credentials, and subscription profiles across the mobile network.
-
B.
UM
UM is the commonly used abbreviation for the University of Miami, a private research university located in Coral Gables, Florida.
-
C.
UM
UM is the regional vehicle registration code used for the district of Uckermark in the German state of Brandenburg.
-
D.
UM
UM is a public research university in Winnipeg, Canada, known as the University of Manitoba.
-
E.
UM
UM is a public research university in Oxford, Mississippi, commonly known as "Ole Miss" and recognized for its academic programs and SEC athletics.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6b197ccb48190a540feecb2d9c70b |
completed | March 27, 2026, 4:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6f7bba1008190a0ea11aabdb3f360 |
completed | March 27, 2026, 9:33 p.m. |
Created at: March 27, 2026, 2:05 p.m.