Triple

T10082756
Position Surface form Disambiguated ID Type / Status
Subject HK33 E213942 entity
Predicate hasVariant P455 FINISHED
Object HK33E E189860 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: HK33E | Statement: [HK33, hasVariant, HK33E]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HK33E
Context triple: [HK33, hasVariant, HK33E]
  • A. HK G3 series chosen
    The HK G3 series is a family of 7.62×51mm NATO battle rifles developed in the 1950s that became one of the most widely used and influential military rifles worldwide.
  • B. HK53
    The HK53 is a compact 5.56×45mm NATO assault rifle developed by Heckler & Koch that combines the roller-delayed blowback system of the G3 family with the size and handling of a submachine gun.
  • C. H3-30
    H3-30 is a specific configuration of Japan’s H3 launch vehicle designed for medium-lift satellite and payload missions.
  • D. HKE
    HKE is the ICAO airline designator for HK Express, a low-cost carrier based in Hong Kong.
  • E. EH53
    EH53 is a postcode district in the EH (Edinburgh) area of Scotland, covering Mid Calder and its surrounding locality in West Lothian.
  • 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_69ca839bf730819086900c323c9b8c95 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdd04352d081908f676444cd2d2578 completed April 2, 2026, 2:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2b66b256c8190861066f7c19008d2 completed April 5, 2026, 7:22 p.m.
Created at: March 30, 2026, 9 p.m.