Triple

T2388710
Position Surface form Disambiguated ID Type / Status
Subject The Monk E48890 entity
Predicate protagonist P268 FINISHED
Object Ambrosio E305416 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: Ambrosio | Statement: [The Monk, protagonist, Ambrosio]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ambrosio
Context triple: [The Monk, protagonist, Ambrosio]
  • A. Ambrosio chosen
    Ambrosio is the devout yet ultimately corrupt and tragic monastic protagonist of Matthew Gregory Lewis’s Gothic novel "The Monk."
  • B. Arsenio
    Arsenio is a masculine given name of Spanish origin, historically borne by several notable figures in Spanish-speaking countries.
  • C. Gonzalo
    Gonzalo is a masculine given name of Spanish origin, historically borne by notable figures such as conquistadors, nobles, and literary characters.
  • D. Fulgencio
    Fulgencio is a Spanish given name most notably borne by Fulgencio Batista, the former Cuban military leader and president.
  • E. Amarildo
    Amarildo is a former Brazilian footballer best known as a forward who starred for Botafogo and the Brazil national team in the early 1960s.
  • 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_69a88aa5f63081908d07fd302029fcbd completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc7dca9248190b634ae9e02f6899a completed March 7, 2026, 6:38 a.m.
NED1 Entity disambiguation (via context triple) batch_69b030fc819c8190a1bd9bba49760fec completed March 10, 2026, 2:55 p.m.
Created at: March 4, 2026, 7:57 p.m.