Triple
T22325611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolshoye Savino Airport |
E551893
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | PEE |
—
|
NE NERFINISHED |
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: PEE | Statement: [Bolshoye Savino Airport, IATAcode, PEE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEE Context triple: [Bolshoye Savino Airport, IATAcode, PEE]
-
A.
PEE
chosen
PEE is the IATA airport code for Perm International Airport, a major air transport hub serving the city of Perm in Russia.
-
B.
PEA
PEA is an Italian film production and distribution company known for its role in European cinema.
-
C.
PEEN
PEEN is a continent-wide ecological network initiative aimed at connecting and conserving natural habitats and biodiversity across Europe.
-
D.
PEP
PEP is the stock ticker symbol for PepsiCo, the multinational food, snack, and beverage corporation traded on the NASDAQ.
-
E.
PNE
PNE is a professional football club based in Preston, Lancashire, England, known for being one of the founding members of the English Football League.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15768696481909be124e86c23d551 |
completed | April 29, 2026, 12:57 a.m. |
Created at: April 16, 2026, 8:42 p.m.