Triple

T12511508
Position Surface form Disambiguated ID Type / Status
Subject Public Law 100-497 E299088 entity
Predicate shortName P43 FINISHED
Object IGRA E287355 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: IGRA | Statement: [Public Law 100-497, shortName, IGRA]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IGRA
Context triple: [Public Law 100-497, shortName, IGRA]
  • A. IGRA chosen
    IGRA is a United States federal law enacted in 1988 that establishes the regulatory framework for gaming operations on Native American tribal lands.
  • B. IGR
    IGR is the IATA airport code for Cataratas del Iguazú International Airport serving Puerto Iguazú in Argentina, a gateway to the Iguazú Falls.
  • C. ISGRG
    ISGRG is a professional scientific society that promotes research and collaboration in general relativity, gravitation, and related fields of physics.
  • D. IRG
    IRG is the commonly used abbreviation for the International Rice Genebank, a major global repository for conserving rice genetic diversity.
  • E. IGU
    IGU is the IATA airport code for Foz do Iguaçu International Airport in Brazil, serving the Iguaçu Falls region.
  • 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_69d6ada4cd388190ae3bbf83ff87057a completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9541d6e508190a4992f328e077467 completed April 10, 2026, 7:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64bb94d608190aae4c8ec39556362 completed May 2, 2026, 7:08 p.m.
Created at: April 8, 2026, 9:57 p.m.