Triple
T12181777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satakunta Air Command |
E290236
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | SATL |
E290236
|
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: SATL | Statement: [Satakunta Air Command, shortName, SATL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SATL Context triple: [Satakunta Air Command, shortName, SATL]
-
A.
SATL
chosen
SATL is the abbreviation for Satakunta Air Command, a unit of the Finnish Air Force responsible for air operations and training.
-
B.
SATI
SATI is an engineering and technology-focused institute in India formally known as Samrat Ashok Technological Institute.
-
C.
SACL
SACL is the corporate entity responsible for operating and managing Sydney Airport in Australia.
-
D.
satsivi
Satsivi is a traditional Georgian cold dish of poultry or vegetables served in a rich, spiced walnut sauce.
-
E.
SACT
SACT is the Supreme Allied Commander Transformation, the NATO strategic commander responsible for leading the alliance’s military transformation and capability development.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d915fd8dac8190928059ad2b6bbbf3 |
completed | April 10, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f6acee6481908ee4129956c98c52 |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:50 p.m.