Triple
T3034265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faro Airport |
E82969
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | LPFR |
E82969
|
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: LPFR | Statement: [Faro Airport, ICAO code, LPFR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LPFR Context triple: [Faro Airport, ICAO code, LPFR]
-
A.
LPFR
chosen
LPFR is the ICAO airport code for Faro Airport, the main international gateway to Portugal’s Algarve region.
-
B.
LLFPA
LLFPA is a U.S. federal law that strengthens workers’ ability to challenge pay discrimination by resetting the statute of limitations with each discriminatory paycheck.
-
C.
LFPG
LFPG is the ICAO airport code for Paris Charles de Gaulle Airport, France’s largest and busiest international air hub.
-
D.
LF
LF is the commonly used abbreviation for the Linux Foundation, a nonprofit organization that supports and promotes the development of the Linux kernel and other open-source software projects.
-
E.
LFPB
LFPB is the ICAO airport code for Paris–Le Bourget Airport, a historic airfield near Paris known for business aviation and the Paris Air Show.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2a40b48190bfa7cdbb0fbd87f8 |
completed | March 8, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1eeeeff988190bb664c75d54d93d8 |
completed | March 11, 2026, 10:38 p.m. |
Created at: March 8, 2026, 3:01 p.m.