Triple

T21099246
Position Surface form Disambiguated ID Type / Status
Subject Agordat E519849 entity
Predicate languageSpoken P151 FINISHED
Object Tigre 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: Tigre | Statement: [Agordat, languageSpoken, Tigre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tigre
Context triple: [Agordat, languageSpoken, Tigre]
  • A. Tigre chosen
    Tigre is a Semitic Afroasiatic language spoken primarily by the Tigre people in Eritrea and parts of Sudan.
  • B. Tigre
    Tigre is a riverside city in the Buenos Aires Province of Argentina, known for its Paraná Delta waterways, tourism, and recreational boating.
  • C. Tigern
    Tigern was a warship that took part in the early 17th-century naval Battle of Oliwa between the Polish–Lithuanian Commonwealth and Sweden.
  • D. Tigri
    Tigri is a locality in South Delhi, India, known primarily as a residential area that also hosts institutions such as the BSF Signal Training School.
  • E. Jagüé
    Jagüé is a small rural village in northwestern Argentina, known as a remote Andean settlement within La Rioja Province.
  • 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_69e0b508d8dc81909be940dafe36c8f7 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e71b5b51608190aa286d89a9d54e9f completed April 21, 2026, 6:38 a.m.
Created at: April 16, 2026, 2:52 p.m.