Triple

T20259347
Position Surface form Disambiguated ID Type / Status
Subject Riga Planning Region E498788 entity
Predicate hasOfficialAbbreviation P8075 FINISHED
Object RPR 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: RPR | Statement: [Riga Planning Region, hasOfficialAbbreviation, RPR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RPR
Context triple: [Riga Planning Region, hasOfficialAbbreviation, RPR]
  • A. RPR chosen
    RPR is the official abbreviation for the Riga Planning Region, an administrative and statistical region centered on Latvia’s capital city.
  • B. RPR
    RPR is the commonly used abbreviation for Rally for the Republic, a former major French Gaullist political party.
  • C. 6PR
    6PR is a Perth-based commercial talk radio station in Western Australia known for its news, talkback, and sports programming.
  • D. PRA
    PRA is the commonly used abbreviation for the Postal Reorganization Act of 1970, the U.S. federal law that transformed the Post Office Department into the United States Postal Service.
  • E. PRA
    PRA is the vehicle registration code for the Polish town of Rawicz in the Greater Poland Voivodeship.
  • 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_69da6275fa6c8190952924930adee150 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e674c84e848190a6e8956698b84026 completed April 20, 2026, 6:47 p.m.
Created at: April 11, 2026, 11:41 p.m.