Triple

T17159614
Position Surface form Disambiguated ID Type / Status
Subject Special Air Service Regiment E416442 entity
Predicate abbreviation P43 FINISHED
Object SASR E416442 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: SASR | Statement: [Special Air Service Regiment, abbreviation, SASR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SASR
Context triple: [Special Air Service Regiment, abbreviation, SASR]
  • A. SASR chosen
    SASR is an elite Australian Army special forces unit renowned for its covert reconnaissance, counter-terrorism, and direct action operations.
  • B. SAS
    SAS is a major Scandinavian airline group that provides passenger and cargo air transport services primarily across Europe and to intercontinental destinations.
  • C. SAS
    SAS is an elite special forces unit of the British Army renowned for its covert operations, counterterrorism expertise, and rigorous selection process.
  • D. SAS
    SAS is the common abbreviation for the San Antonio Silver Stars, a former Women’s National Basketball Association (WNBA) team based in San Antonio, Texas.
  • E. SAS
    SAS is the standard abbreviation used for the Canadian Football League team Saskatchewan Roughriders.
  • 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_69d886d279c081909f8ff1f743ddeb69 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f9103e3881908e76cea1c4880779 completed April 18, 2026, 9:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0148376bc081908372366203a27fa8 completed May 11, 2026, 3:08 a.m.
Created at: April 10, 2026, 5:37 a.m.