Triple
T5816390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 1 (Lisbon Airport) |
E128996
|
entity |
| Predicate | IATAAirportCodeOfParent |
P2569
|
FINISHED |
| Object | LIS |
E106458
|
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: LIS | Statement: [Terminal 1 (Lisbon Airport), IATAAirportCodeOfParent, LIS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LIS Context triple: [Terminal 1 (Lisbon Airport), IATAAirportCodeOfParent, LIS]
-
A.
LIS
chosen
LIS is the three-letter IATA airport code for Humberto Delgado Airport, the main international airport serving Lisbon, Portugal.
-
B.
litas
The litas was the national currency of Lithuania before the adoption of the euro.
-
C.
LCS
LCS is North America's premier professional League of Legends esports league, featuring top teams competing in seasonal splits and playoffs.
-
D.
Litas
Litas is the former official currency of Lithuania, used before the country adopted the euro.
-
E.
PTLIS
PTLIS is the UN/LOCODE designation for the port and city of Lisbon, Portugal, used in international trade and transport documentation.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c033e207608190926a0b10fe157a13 |
completed | March 22, 2026, 6:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c098504c68819089eff37ea1fa0979 |
completed | March 23, 2026, 1:33 a.m. |
Created at: March 22, 2026, 3:53 p.m.