Triple
T1959210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maximilian I of Mexico |
E42341
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ferdinand |
E60224
|
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: Ferdinand | Statement: [Maximilian I of Mexico, givenName, Ferdinand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ferdinand Context triple: [Maximilian I of Mexico, givenName, Ferdinand]
-
A.
Ferdinand
chosen
Ferdinand is a masculine given name of Germanic origin historically borne by numerous European nobles and monarchs.
-
B.
Fernando
Fernando is the given name of Salgueiro Maia, a key Portuguese military officer who played a leading role in the Carnation Revolution.
-
C.
Alfonso
Alfonso is a masculine given name of Spanish and Italian origin historically borne by numerous kings, nobles, and notable figures across Europe.
-
D.
Carlos
Carlos is a common Spanish given name widely used across Spanish-speaking countries and communities.
-
E.
Guillermo
Guillermo is the Spanish form of the given name William, 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb37f737881908130bb828affcaa2 |
completed | March 7, 2026, 5:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adfbcea048819091d705095f0d3f68 |
completed | March 8, 2026, 10:44 p.m. |
Created at: March 4, 2026, 7:36 p.m.