Triple

T18923044
Position Surface form Disambiguated ID Type / Status
Subject VRU E462909 entity
Predicate shortName P43 FINISHED
Object VRU 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: VRU | Statement: [VRU, shortName, VRU]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: VRU
Context triple: [VRU, shortName, VRU]
  • A. VRU chosen
    VRU is the commonly used Ukrainian abbreviation for the Verkhovna Rada, the unicameral parliament and supreme legislative body of Ukraine.
  • B. VRG
    VRG is the ICAO airline designator for Varig, the former Brazilian flag carrier and one of Latin America's historically significant airlines.
  • C. VRT
    VRT is Belgium’s public-service broadcaster for the Flemish Community, providing television, radio, and online media.
  • D. VR&E
    VR&E is a U.S. Department of Veterans Affairs program that helps eligible veterans and service members with service-connected disabilities prepare for, find, and maintain suitable employment or achieve independent living.
  • E. VRS
    VRS is the acronym for the Army of Republika Srpska, the Bosnian Serb military force active during the Bosnian War in the 1990s.
  • 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_69d8dcfdbbb881909964fa5a75bd0b48 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c9b4822c8190a0aeceb4499e775e completed April 20, 2026, 6:37 a.m.
Created at: April 10, 2026, 11:59 a.m.