Triple
T21083830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Iranian security services |
E519436
|
entity |
| Predicate | replacedBy |
P101
|
FINISHED |
| Object | SAVAMA |
—
|
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: SAVAMA | Statement: [Imperial Iranian security services, replacedBy, SAVAMA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SAVAMA Context triple: [Imperial Iranian security services, replacedBy, SAVAMA]
-
A.
SAVAMA
chosen
SAVAMA was the post-revolution Iranian intelligence and security organization that succeeded the Shah’s notorious secret police, SAVAK.
-
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.
SAVV
SAVV is the ICAO airport code assigned to Gobernador Edgardo Castello Airport in Argentina.
-
E.
SAAV
SAAV is the ICAO airport code for Sauce Viejo Airport, which serves the Santa Fe region 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e70948704481908b8b75a2ecc42bb6 |
completed | April 21, 2026, 5:21 a.m. |
Created at: April 16, 2026, 2:49 p.m.