Triple

T17130597
Position Surface form Disambiguated ID Type / Status
Subject Allied intelligence services E415711 entity
Predicate hasPart P35 FINISHED
Object GRU E208812 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: GRU | Statement: [Allied intelligence services, hasPart, GRU]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GRU
Context triple: [Allied intelligence services, hasPart, GRU]
  • A. GRU chosen
    GRU is Russia’s military intelligence agency, known for conducting espionage, cyber operations, and covert activities abroad.
  • B. GRU
    GRU is the IATA airport code for São Paulo–Guarulhos International Airport, the main international gateway serving São Paulo, Brazil.
  • C. GRU
    GRU is the abbreviation for the Georgian Rugby Union, the governing body responsible for overseeing and developing rugby union in Georgia.
  • D. RBM
    RBM is a global partnership initiative dedicated to coordinating and scaling up efforts to prevent, control, and ultimately eliminate malaria worldwide.
  • E. NN
    NN is the postcode area in the United Kingdom that covers Northampton and surrounding parts of Northamptonshire.
  • 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_69d886d15af4819092f92f8a129763e6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f029d1a48190a9d4094827d11d23 completed April 18, 2026, 8:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01414cd5d481908d11eb230d2283cd completed May 11, 2026, 2:39 a.m.
Created at: April 10, 2026, 5:36 a.m.