Triple

T12274339
Position Surface form Disambiguated ID Type / Status
Subject La Araucana E292551 entity
Predicate hasCharacter P2308 FINISHED
Object Caupolicán E292554 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: Caupolicán | Statement: [La Araucana, hasCharacter, Caupolicán]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Caupolicán
Context triple: [La Araucana, hasCharacter, Caupolicán]
  • A. Caupolicán chosen
    Caupolicán was a prominent Mapuche toqui (war leader) celebrated in Chilean history and literature for leading indigenous resistance against Spanish conquest in the 16th century.
  • B. Raimundo
    Raimundo is a masculine given name of Spanish and Portuguese origin, related to the name Ramón and ultimately derived from the Germanic name Raymond.
  • C. Martín de Osambela
    Martín de Osambela was a prominent Spanish merchant and landowner in colonial Lima, Peru, known for his wealth and influence in the late 18th and early 19th centuries.
  • D. Ramiro
    Ramiro is a masculine given name of Spanish and Portuguese origin, historically borne by several medieval kings and nobles in the Iberian Peninsula.
  • E. Teobaldo
    Teobaldo is the Italian form of the given name Theobald, historically borne by various European nobles and clerics.
  • 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_69d6ab6856488190b5d31178d5015f8e completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91cef684081908adaee8e04facc2e completed April 10, 2026, 3:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69f61e6b50a48190b1beabd149d5830f completed May 2, 2026, 3:55 p.m.
Created at: April 8, 2026, 9:52 p.m.