Triple

T20629009
Position Surface form Disambiguated ID Type / Status
Subject Paulus Henrique Benedictus Cox E506898 entity
Predicate hasGivenName P17 FINISHED
Object Henrique 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: Henrique | Statement: [Paulus Henrique Benedictus Cox, hasGivenName, Henrique]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Henrique
Context triple: [Paulus Henrique Benedictus Cox, hasGivenName, Henrique]
  • A. Henrique chosen
    Henrique is a masculine given name of Portuguese origin commonly used in Portuguese- and Spanish-speaking countries.
  • B. Sebastião
    Sebastião is the Portuguese variant of the given name Sebastian, commonly used in Portuguese-speaking countries.
  • C. Guilherme
    Guilherme is the Portuguese form of the given name William, commonly used in Portuguese-speaking countries.
  • D. António
    António is a common Portuguese given name, notably borne by António Guterres, the Secretary-General of the United Nations.
  • E. Manoel
    Manoel is a given name, commonly used in Portuguese- and Spanish-speaking cultures, that is a variant of the name Emmanuel.
  • 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_69e0b4bd4a0081908d4e97a590a33fb2 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6abe771e88190a48471bf83b4804d completed April 20, 2026, 10:42 p.m.
Created at: April 16, 2026, 11:42 a.m.