Triple
T22619245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comodoro Rivadavia Airport |
E558228
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | SAVC |
—
|
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: SAVC | Statement: [Comodoro Rivadavia Airport, ICAOcode, SAVC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SAVC Context triple: [Comodoro Rivadavia Airport, ICAOcode, SAVC]
-
A.
SAVC
chosen
SAVC is the ICAO airport code for General Enrique Mosconi International Airport in Comodoro Rivadavia, Argentina.
-
B.
SAV
SAV is the National Rail station code for Stratford-upon-Avon railway station in Warwickshire, England.
-
C.
SAV
SAV is the IATA airport code for Savannah/Hilton Head International Airport serving Savannah, Georgia, and the surrounding region.
-
D.
SAVP
SAVP is a profile or configuration associated with the Real-time Transport Protocol (RTP), typically used to define specific parameters or behaviors for secure or specialized media streaming sessions.
-
E.
SAVV
SAVV is the ICAO airport code assigned to Gobernador Edgardo Castello Airport in Argentina.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e377ae88190832edfdfbc3ed58f |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 3 p.m.