Triple
T13902887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macon Downtown Airport |
E334271
|
entity |
| Predicate | usesCode |
P24101
|
FINISHED |
| Object | MAC |
E334271
|
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: MAC | Statement: [Macon Downtown Airport, usesCode, MAC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MAC Context triple: [Macon Downtown Airport, usesCode, MAC]
-
A.
MAC
MAC is the acronym for the Military Armistice Commission, the body responsible for supervising the implementation of the Korean Armistice Agreement.
-
B.
MAC
The MAC is a regional museum in Spokane, Washington, featuring art, history, and cultural exhibits focused on the Inland Northwest.
-
C.
MAC
MAC is the common abbreviation for the Macon Bacon, a collegiate summer baseball team based in Macon, Georgia.
-
D.
MAC
The MAC is an NCAA Division III athletic conference in the Middle Atlantic region of the United States, sponsoring intercollegiate sports among its member colleges and universities.
-
E.
MAC
chosen
MAC is the IATA airport code for Macon Downtown Airport, a public airport serving the city of Macon, Georgia, in the United States.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25db1e308190aaed6a21e443cc44 |
completed | April 14, 2026, 11:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fba1c26ba08190b19560123691fda4 |
completed | May 6, 2026, 8:17 p.m. |
Created at: April 9, 2026, 10:16 p.m.