Triple
T6459588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hrodebert |
E142081
|
entity |
| Predicate | isCognateWith |
P2527
|
FINISHED |
| Object | Roberto (Portuguese given name) |
E26746
|
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: Roberto (Portuguese given name) | Statement: [Hrodebert, isCognateWith, Roberto (Portuguese given name)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Roberto (Portuguese given name) Context triple: [Hrodebert, isCognateWith, Roberto (Portuguese given name)]
-
A.
Roberto
chosen
Roberto is a masculine given name commonly used in Romance-language countries, equivalent to the English name Robert.
-
B.
João
João is a common Portuguese male given name widely used in Portuguese-speaking countries, equivalent to "John" in English.
-
C.
Gonçalo
Gonçalo is a Portuguese given name, equivalent to the Spanish name Gonzalo and commonly used for males in Portuguese-speaking countries.
-
D.
Joaquim
Joaquim is a given name used in certain languages as a variant of Saint Joachim, traditionally regarded as the father of the Virgin Mary in Christian tradition.
-
E.
Sérgio
Sérgio is a Portuguese given name commonly used in Brazil and other Lusophone countries.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069f347f48190a2b22c5b648b17bd |
completed | March 22, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c64be1fad88190af07b7053811e3f2 |
completed | March 27, 2026, 9:20 a.m. |
Created at: March 22, 2026, 4:48 p.m.