Triple
T13587819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenderal Ahmad Yani International Airport |
E324614
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | SRG |
E324614
|
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: SRG | Statement: [Jenderal Ahmad Yani International Airport, IATACode, SRG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SRG Context triple: [Jenderal Ahmad Yani International Airport, IATACode, SRG]
-
A.
SRG
chosen
SRG is the IATA airport code for Jenderal Ahmad Yani International Airport serving Semarang, Indonesia.
-
B.
SRB
SRB is the commonly used abbreviation for Sveriges Riksbank, the central bank of Sweden and the world’s oldest central bank.
-
C.
SRB
SRB is the three-letter ISO 3166-1 alpha-3 country code assigned to Serbia.
-
D.
SRB
The SRB is the European Union agency responsible for managing the orderly resolution of failing banks within the Banking Union to protect financial stability and taxpayers.
-
E.
SRB
SRB is a powerful solid-fuel rocket component used to provide major thrust during the initial phase of a spacecraft’s launch.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb054c6008190839384ce26e8f71a |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bc347b881908267455f3bdd50e8 |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.