Triple

T6776967
Position Surface form Disambiguated ID Type / Status
Subject Apurinã language E155581 entity
Predicate autonym P1435 FINISHED
Object Ipurinã E598486 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: Ipurinã | Statement: [Apurinã language, autonym, Ipurinã]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ipurinã
Context triple: [Apurinã language, autonym, Ipurinã]
  • A. Guapimirim
    Guapimirim is a municipality in the state of Rio de Janeiro, Brazil, known for its mountainous landscapes and protected natural areas near Guanabara Bay.
  • B. Pirassununga
    Pirassununga is a municipality in the state of São Paulo, Brazil, known for its agricultural activities and as a site of a major University of São Paulo campus.
  • C. Puruborá chosen
    Puruborá is an indigenous language of Brazil belonging to the Tupian family, traditionally spoken by the Puruborá people of the Amazon region.
  • D. Quixeramobim
    Quixeramobim is a municipality in northeastern Brazil known for its semi-arid landscape and agricultural activities within the state of Ceará.
  • E. Itapevi
    Itapevi is a municipality in the metropolitan region of São Paulo, Brazil, known for its growing industrial sector and residential expansion.
  • 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_69c688162bf8819088b664b5c3b5be7a completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d26725208190b64935cfd08b2aff completed March 27, 2026, 6:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c712cc9ff08190bb7ec0bf4cc4db01 completed March 27, 2026, 11:29 p.m.
Created at: March 27, 2026, 2:13 p.m.