Triple
T4212386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tocumen International Airport |
E93933
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | PTY |
E221235
|
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: PTY | Statement: [Tocumen International Airport, IATAcode, PTY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PTY Context triple: [Tocumen International Airport, IATAcode, PTY]
-
A.
PTY
chosen
PTY is the IATA airport code for Tocumen International Airport, the main international gateway serving Panama City, Panama.
-
B.
PLY
PLY is the National Rail station code for Plymouth railway station, a major rail hub in Plymouth, Devon, England.
-
C.
PTR
PTR was the abbreviation for the Physikalisch-Technische Reichsanstalt, the German national institute for standards and scientific-technical metrology in the early 20th century.
-
D.
PT
PT is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Portugal in international standards and systems.
-
E.
PT
PT is the time standard used along the west coast of North America, including cities like Los Angeles, San Francisco, and Vancouver.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34be585848190b0b177b5516f53c1 |
completed | March 12, 2026, 11:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b59631e2cc8190b1d125b82a81593e |
completed | March 14, 2026, 5:09 p.m. |
Created at: March 12, 2026, 11:04 p.m.