Triple

T17582071
Position Surface form Disambiguated ID Type / Status
Subject USS Mount McKinley E428226 entity
Predicate callSign P1565 FINISHED
Object AGC-7 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: AGC-7 | Statement: [USS Mount McKinley, callSign, AGC-7]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AGC-7
Context triple: [USS Mount McKinley, callSign, AGC-7]
  • A. AGC-7 chosen
    AGC-7 was the hull classification symbol for USS Mount McKinley, a U.S. Navy amphibious force command ship that served as a flagship in major World War II and postwar operations.
  • B. Kokusai Ta-Go
    The Kokusai Ta-Go was a late-World War II Japanese prototype light fighter aircraft designed for emergency home-defense use.
  • C. Kokusai Ku-7 Manazuru
    The Kokusai Ku-7 Manazuru was a large Japanese World War II military transport glider designed to carry heavy cargo and vehicles.
  • D. Unternehmen Taifun
    Unternehmen Taifun, or Operation Typhoon, was Nazi Germany’s 1941 military offensive aimed at capturing Moscow during World War II.
  • E. Akagi Daimyōjin
    Akagi Daimyōjin is a Shinto deity associated with Mount Akagi and revered as the principal kami of Akagi Shrine in Japan.
  • 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_69d889e1030481909950e140c63255b9 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e463ce8eb081909257be47d150aa04 completed April 19, 2026, 5:10 a.m.
Created at: April 10, 2026, 5:50 a.m.