Triple
T8105866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adolfo Pérez Esquivel |
E189223
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Adolfo |
E480447
|
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: Adolfo | Statement: [Adolfo Pérez Esquivel, givenName, Adolfo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adolfo Context triple: [Adolfo Pérez Esquivel, givenName, Adolfo]
-
A.
Adolfo
chosen
Adolfo is a masculine given name, commonly used in Spanish and Italian, that derives from the Germanic name Adolf.
-
B.
Alfons
Alfons is the given name of Alphonse Mucha, the renowned Czech Art Nouveau painter and decorative artist.
-
C.
Humberto
Humberto is a masculine given name of Spanish and Portuguese origin, commonly used in Iberian and Latin American countries.
-
D.
Eugenio
Eugenio is a masculine given name of Greek origin, commonly used in Spanish- and Italian-speaking countries.
-
E.
Silvano
Silvano is an Italian given name, related to Silvio, traditionally associated with the Latin name Silvanus meaning "of the forest" or "woodland."
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42f735c8819090d0d822644c0a51 |
completed | March 31, 2026, 3:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccbe8e3fc88190aaf3bbfa54f4c8ec |
completed | April 1, 2026, 6:43 a.m. |
Created at: March 30, 2026, 5:31 p.m.