Triple
T23041704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molokaʻi Airport |
E573753
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | PHMK |
—
|
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: PHMK | Statement: [Molokaʻi Airport, ICAO code, PHMK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PHMK Context triple: [Molokaʻi Airport, ICAO code, PHMK]
-
A.
PHMK
chosen
PHMK is the ICAO airport code for Molokaʻi Airport, a public airport serving the island of Molokaʻi in Hawaii.
-
B.
PMK
PMK is a regional political party in the Indian state of Tamil Nadu, primarily representing Vanniyar community interests and allied at various times with major national and state parties.
-
C.
PH-MAD
PH-MAD is the ISO 3166-2:PH subdivision code assigned to the Philippine province of Marinduque.
-
D.
PHMNL
PHMNL is the UN/LOCODE identifier for the Port of Manila in the Philippines, used in international trade and shipping logistics.
-
E.
PKM
PKM is a Polish metropolitan railway line serving the Pomeranian region, particularly improving commuter connections around Gdańsk.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18513fc54819096d761a0be75b774 |
completed | April 29, 2026, 4:12 a.m. |
Created at: April 17, 2026, 3:54 p.m.