Triple
T12975726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francisco Sá Carneiro Airport |
E321518
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | LPPR |
E921503
|
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: LPPR | Statement: [Francisco Sá Carneiro Airport, ICAOcode, LPPR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LPPR Context triple: [Francisco Sá Carneiro Airport, ICAOcode, LPPR]
-
A.
LPPR
chosen
LPPR is the ICAO airport code for Francisco Sá Carneiro Airport, the international airport serving Porto, Portugal.
-
B.
LPP
LPP is the IATA airport code for Lappeenranta Airport in Lappeenranta, Finland.
-
C.
LPPD
LPPD is the ICAO airport code for João Paulo II Airport, the main international airport serving Ponta Delgada in the Azores, Portugal.
-
D.
PRR
PRR is the abbreviation commonly used for the Pennsylvania Railroad Company, once one of the largest and most influential railroads in the United States.
-
E.
PRR
PRR is a set of UK financial regulations governing the content and approval of prospectuses for securities offerings to protect investors and ensure market transparency.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e48c0208190bb7ec80780480b37 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8ec821c81909398d8e02d69dcbf |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 8:37 p.m.