Triple
T20354293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SKW |
E496101
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SKW |
—
|
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: SKW | Statement: [SKW, abbreviation, SKW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SKW Context triple: [SKW, abbreviation, SKW]
-
A.
SKW
chosen
SKW is Poland’s Military Counterintelligence Service, responsible for protecting the armed forces and state defense structures from espionage, terrorism, and other security threats.
-
B.
SKW
SKW is the ICAO airline designator used to identify SkyWest Airlines in aviation operations and communications.
-
C.
SKO
SKO is the abbreviation for the Saito Kinen Orchestra, a renowned Japanese classical ensemble founded by conductor Seiji Ozawa in honor of his teacher Hideo Saito.
-
D.
SKO
SKO is the IATA airport code for Sadiq Abubakar III International Airport serving Sokoto, Nigeria.
-
E.
SKB
SKB is the German Bundeswehr’s Joint Support Service, responsible for providing cross-branch logistical, administrative, and operational support to the armed forces.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67852ca9881908a5af18005639859 |
completed | April 20, 2026, 7:02 p.m. |
Created at: April 16, 2026, 11:25 a.m.