Triple
T14410716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arturo Alfonso Schomburg |
E357316
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Arturo |
E243576
|
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: Arturo | Statement: [Arturo Alfonso Schomburg, givenName, Arturo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arturo Context triple: [Arturo Alfonso Schomburg, givenName, Arturo]
-
A.
Arturo
chosen
Arturo is a masculine given name of Spanish and Italian origin, equivalent to Arthur in English.
-
B.
Eugenio
Eugenio is a masculine given name of Greek origin, commonly used in Spanish- and Italian-speaking countries.
-
C.
Eduardo
Eduardo is a masculine given name commonly used in Spanish and Portuguese-speaking countries, equivalent to the English name Edward.
-
D.
Arsenio
Arsenio is a masculine given name of Spanish origin, historically borne by several notable figures in Spanish-speaking countries.
-
E.
Ernesto
Ernesto is a masculine given name of Spanish origin commonly used in Spanish-speaking 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90c9b3448190aec1608836a5e913 |
completed | April 14, 2026, 7:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0cd3aa20819089c8527faf1ceddd |
completed | May 8, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:17 a.m.