Triple
T14870281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MZN |
E349724
|
entity |
| Predicate | ISO4217Code |
P189
|
FINISHED |
| Object | MZN |
E349724
|
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: MZN | Statement: [MZN, ISO4217Code, MZN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MZN Context triple: [MZN, ISO4217Code, MZN]
-
A.
MZN
MZN is the ICAO airline designator used to identify Amazon Air flights in international aviation operations.
-
B.
MZN
chosen
MZN is the official currency code for the Mozambican metical, the national currency of Mozambique.
-
C.
MNZ
MNZ is the IATA airport code for Manassas Regional Airport, a public airport serving Manassas, Virginia, in the United States.
-
D.
MNZM
MNZM is a post-nominal honorific used to denote a Member of the New Zealand Order of Merit, recognizing significant service to the Crown and nation.
-
E.
MZ
MZ is the vehicle registration code for the Mainz region in Germany, which includes Ingelheim am Rhein.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded57967748190a7c05ebb74aacb7c |
completed | April 15, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe651067cc8190b9c218ef1f802762 |
completed | May 8, 2026, 10:34 p.m. |
Created at: April 10, 2026, 1:55 a.m.