Triple
T14902572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hendrika |
E360042
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Henriqué |
E428331
|
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: Henriqué | Statement: [Hendrika, hasCognate, Henriqué]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Henriqué Context triple: [Hendrika, hasCognate, Henriqué]
-
A.
Henrique
chosen
Henrique is a masculine given name of Portuguese origin commonly used in Portuguese- and Spanish-speaking countries.
-
B.
Luís
Luís is a common Portuguese male given name, historically associated with notable figures such as the poet Luís de Camões.
-
C.
Felipe de Barbacena
Felipe de Barbacena was a Brazilian military leader and nobleman who played a prominent command role in Brazil’s early 19th-century conflicts, including the Cisplatine War.
-
D.
José, Prince of Brazil
José, Prince of Brazil was the eldest son and heir apparent of Queen Maria I of Portugal who died young, preventing him from ascending the throne.
-
E.
John, Prince of Brazil
John, Prince of Brazil was the heir apparent to the Portuguese throne who later became King John VI of Portugal, Brazil, and the Algarves.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded60b24008190bd272c0d61329400 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe72b4e4f88190af7e859d93dbbd28 |
completed | May 8, 2026, 11:33 p.m. |
Created at: April 10, 2026, 2:11 a.m.