Triple
T15346335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulgencio Yegros |
E366928
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Fulgencio |
E157212
|
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: Fulgencio | Statement: [Fulgencio Yegros, givenName, Fulgencio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fulgencio Context triple: [Fulgencio Yegros, givenName, Fulgencio]
-
A.
Fulgencio
chosen
Fulgencio is a Spanish given name most notably borne by Fulgencio Batista, the former Cuban military leader and president.
-
B.
Niceto
Niceto is the given name of Niceto Alcalá-Zamora, the first President of the Second Spanish Republic.
-
C.
Teodorito
Teodorito is a Spanish diminutive form of the given name Teodoro, typically used as an affectionate or familiar nickname.
-
D.
José Antonio
José Antonio is a common Spanish male given name widely used across Spain and Latin America, often associated with historical, political, and cultural figures.
-
E.
Emiliano
Emiliano is a masculine given name of Spanish and Italian origin, derived from the Roman family name Aemilius.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e1749bc8190a8b9cbcb27288a5b |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01f931408190828d87567cecaceb |
completed | May 9, 2026, 9:44 a.m. |
Created at: April 10, 2026, 3:17 a.m.