Triple
T10653456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umkhonto we Sizwe |
E251029
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | MK |
E251029
|
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: MK | Statement: [Umkhonto we Sizwe, abbreviation, MK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MK Context triple: [Umkhonto we Sizwe, abbreviation, MK]
-
A.
MK
MK is the two-letter ISO 3166-1 alpha-2 country code assigned to North Macedonia.
-
B.
MK
chosen
MK is the commonly used abbreviation for Umkhonto we Sizwe, the former armed wing of South Africa’s African National Congress during the anti-apartheid struggle.
-
C.
MK
MK is the postal area code designation for Milton Keynes and its surrounding region in the United Kingdom.
-
D.
MK
MK is the two-letter IATA airline designator assigned to Air Mauritius, the flag carrier airline of Mauritius.
-
E.
M-K
M-K is the commonly used abbreviation for Morrison-Knudsen, a major American engineering and construction company known for large-scale infrastructure projects.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff85674819099bf40c9f4fede15 |
completed | April 8, 2026, 11:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d97a71fac48190a6d7c99ebc5aad0a |
completed | April 10, 2026, 10:32 p.m. |
Created at: April 8, 2026, 9:06 p.m.