Triple
T18273313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMM |
E437667
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | AMM |
—
|
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: AMM | Statement: [AMM, IATACode, AMM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AMM Context triple: [AMM, IATACode, AMM]
-
A.
AMM
chosen
AMM is the IATA airport code for Queen Alia International Airport, the main international gateway serving Amman, Jordan.
-
B.
AMM
AMM is the standard abbreviation for the American Mathematical Monthly, a leading journal that publishes expository articles in mathematics.
-
C.
AMM
AMM is the commonly used abbreviation for the APEC Ministerial Meeting, the annual gathering of Asia-Pacific Economic Cooperation foreign and trade ministers.
-
D.
AMMC
AMMC is Morocco’s financial markets authority responsible for regulating and supervising the country’s capital markets and securities activities.
-
E.
Amm
Amm is an ancient South Arabian god, particularly revered in the Qataban kingdom as a principal deity associated with protection and tribal identity.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5005006108190bbddddbe6bbdc911 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 10:34 a.m.