Triple
T2514018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alphonso, Earl of Chester |
E52767
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Alphonso |
E162427
|
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: Alphonso | Statement: [Alphonso, Earl of Chester, givenName, Alphonso]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alphonso Context triple: [Alphonso, Earl of Chester, givenName, Alphonso]
-
A.
Calixto
Calixto is a masculine given name of Spanish origin, historically borne by several notable Latin American figures.
-
B.
Alfonso
chosen
Alfonso is a masculine given name of Spanish and Italian origin historically borne by numerous kings, nobles, and notable figures across Europe.
-
C.
Guillermo
Guillermo is the Spanish form of the given name William, commonly used in Spanish-speaking countries.
-
D.
Eduardo
Eduardo is a masculine given name commonly used in Spanish and Portuguese-speaking countries, equivalent to the English name Edward.
-
E.
Timoteo
Timoteo is a masculine given name, commonly used in Romance-language countries, derived from the biblical name Timothy.
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd20c8ab0819096d6a654039beb39 |
completed | March 7, 2026, 7:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af2b934d3c81909627a5f4d6e6ca6a |
completed | March 9, 2026, 8:20 p.m. |
Created at: March 6, 2026, 9:46 p.m.