Triple
T11788527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rovaniemi Airport |
E280331
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | EFRO |
E280330
|
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: EFRO | Statement: [Rovaniemi Airport, ICAO code, EFRO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EFRO Context triple: [Rovaniemi Airport, ICAO code, EFRO]
-
A.
EFRO
chosen
EFRO is the ICAO airport code for Rovaniemi Air Base in Finland, which serves both military and civilian air traffic near the Arctic Circle.
-
B.
EF
EF is the commonly used abbreviation for the Eclipse Foundation, a nonprofit organization that oversees open-source software projects and the Eclipse IDE ecosystem.
-
C.
FRO
FRO is the three-letter ISO 3166-1 alpha-3 country code assigned to the Faroe Islands.
-
D.
FEF
FEF is the commonly used abbreviation for the Ecuadorian Football Federation, the governing body of football in Ecuador.
-
E.
OFROU
OFROU is the Swiss Federal Roads Office, the national authority responsible for planning, constructing, and maintaining Switzerland’s national road network and related traffic policies.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a587c2d881909297c3a6c7d26080 |
completed | April 10, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f166c735008190a73dd74dbcddd182 |
completed | April 29, 2026, 2:02 a.m. |
Created at: April 8, 2026, 9:42 p.m.