Triple
T22496825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew |
E556162
|
entity |
| Predicate | equivalentNameInLanguage |
P63334
|
FINISHED |
| Object | Mateus (Portuguese) |
—
|
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: Mateus (Portuguese) | Statement: [Matthew, equivalentNameInLanguage, Mateus (Portuguese)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mateus (Portuguese) Context triple: [Matthew, equivalentNameInLanguage, Mateus (Portuguese)]
-
A.
Matheus (Portuguese)
Matheus is a Portuguese given name, equivalent to Matthew, commonly used in Portuguese-speaking countries.
-
B.
Matheus (German)
Matheus is the German form of the given name Matthew, sharing the same biblical origin and meaning of “gift of God.”
-
C.
Matheus
Matheus is a given name, commonly used in Portuguese-speaking countries, that is a variant of the name Matthew.
-
D.
Mateus
chosen
Mateus is a Portuguese surname commonly borne by individuals such as Rui Mateus.
-
E.
Arturo (Portuguese)
Arturo (Portuguese) is the Portuguese form of the given name Arthur, commonly used in Lusophone countries.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb2644c819094864bd88bcebcbd |
completed | April 29, 2026, 1:19 a.m. |
Created at: April 16, 2026, 8:50 p.m.