Triple

T21082280
Position Surface form Disambiguated ID Type / Status
Subject Next Generation Identification E519398 entity
Predicate alsoKnownAs P39 FINISHED
Object NGI 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: NGI | Statement: [Next Generation Identification, alsoKnownAs, NGI]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: NGI
Context triple: [Next Generation Identification, alsoKnownAs, NGI]
  • A. NGI chosen
    NGI (Next Generation Identification) is the FBI’s advanced biometric identification system that expands and modernizes fingerprint and related data services for law enforcement and national security.
  • B. NGI
    NGI is the vehicle registration code assigned to the municipality of Ryn in Poland.
  • C. NGI
    NGI is a research consortium focused on studying and addressing environmental and ecological issues in the northern Gulf of Mexico region.
  • D. ngi
    ngi is the ISO 639-3 language code for Ngizim, a West Chadic language spoken primarily in northeastern Nigeria.
  • E. NGU
    NGU is the acronym for the National Guard of Ukraine, a military formation responsible for national defense, public order, and internal security.
  • 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_69e0b506e59c8190849b71ed07929215 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e702dcbf9c81908e4cc016eb21bbbc completed April 21, 2026, 4:53 a.m.
Created at: April 16, 2026, 2:49 p.m.