Triple
T16352857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Armed Forces |
E397101
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SAF |
E397101
|
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: SAF | Statement: [Swiss Armed Forces, abbreviation, SAF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SAF Context triple: [Swiss Armed Forces, abbreviation, SAF]
-
A.
SAF
SAF is the three-letter IATA airport code for Santa Fe Regional Airport in Santa Fe, New Mexico.
-
B.
SAF
chosen
SAF is the abbreviation commonly used for the Swiss Armed Forces, the military organization responsible for Switzerland’s national defense.
-
C.
SAF
SAF is the acronym for the Singapore Armed Forces, the military organization responsible for the defense of Singapore.
-
D.
SAF/AQ
SAF/AQ is the U.S. Air Force headquarters organization responsible for overseeing acquisition, technology development, and logistics programs across the service.
-
E.
Safis
The Safis are a Pashtun tribal group historically associated with the Mohmand region along the Afghanistan–Pakistan border.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2faccab748190b11e0808e422f2ea |
completed | April 18, 2026, 3:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a002db6375c81908c64dbe2bc987b1a |
completed | May 10, 2026, 7:03 a.m. |
Created at: April 10, 2026, 5:07 a.m.