Triple
T1344207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisbon Airport |
E28532
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | LPPT |
E106459
|
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: LPPT | Statement: [Lisbon Airport, ICAOcode, LPPT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LPPT Context triple: [Lisbon Airport, ICAOcode, LPPT]
-
A.
LPPT
chosen
LPPT is the ICAO airport code for Humberto Delgado Airport, the main international airport serving Lisbon, Portugal.
-
B.
LPFR
LPFR is the ICAO airport code for Faro Airport, the main international gateway to Portugal’s Algarve region.
-
C.
LMT
LMT is the stock ticker symbol for Lockheed Martin Corporation, a major American aerospace, defense, and security company.
-
D.
LWP
LWP is the abbreviation for the Polish People’s Army, the communist-era armed forces of Poland that existed from the end of World War II until 1989.
-
E.
LCC
LCC is a comprehensive library classification system developed by the Library of Congress to organize and arrange books and other materials by subject.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23b8a9081908b78405d4ef806af |
completed | March 1, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acc6351cbc81909e2ffc692ee92b54 |
completed | March 8, 2026, 12:43 a.m. |
Created at: March 1, 2026, 7:56 p.m.