Triple
T12006987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faro |
E285804
|
entity |
| Predicate | hasAirportICAOCode |
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, hasAirportICAOCode, LPFR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LPFR Context triple: [Faro, hasAirportICAOCode, LPFR]
-
A.
LPFR
chosen
LPFR is the ICAO airport code for Faro Airport, the main international gateway to Portugal’s Algarve region.
-
B.
LFRS
LFRS is the ICAO airport code for Nantes Atlantique Airport, a major international airport serving the city of Nantes in western France.
-
C.
LFRJ
LFRJ is the ICAO airport code for BAN Landivisiau, a French naval air base and military airfield in Brittany, France.
-
D.
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.
-
E.
LFRL
LFRL is the ICAO airport code for the French naval air base at Lanvéoc-Poulmic in Brittany.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c5cfc08190821e4b2940c51416 |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48b1570208190a08c64e028f67d81 |
completed | May 1, 2026, 11:14 a.m. |
Created at: April 8, 2026, 9:46 p.m.