Triple
T22827608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afonso |
E565702
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Afonso |
—
|
NE NERFINISHED |
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: Afonso | Statement: [Afonso, hasVariant, Afonso]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Afonso Context triple: [Afonso, hasVariant, Afonso]
-
A.
Afonso
Afonso is a Portuguese surname most notably borne by the renowned geometric abstractionist painter and architect Nadir Afonso.
-
B.
Afonso
chosen
Afonso is a Portuguese given name historically borne by several kings of Portugal and associated with medieval Iberian nobility.
-
C.
Afonso the Brave
Afonso the Brave is the epithet of Afonso IV, a 14th-century King of Portugal known for his military campaigns and consolidation of royal power.
-
D.
António
António is a common Portuguese given name, notably borne by António Guterres, the Secretary-General of the United Nations.
-
E.
Afonso Gonçalves
Afonso Gonçalves was a Portuguese sailor and explorer who served in the pioneering early voyages of Portugal’s maritime expansion to India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2914188190be6cdbd8167cd806 |
completed | April 29, 2026, 3:42 a.m. |
Created at: April 17, 2026, 3:34 p.m.