Triple
T26538600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Wellesley |
E671320
|
entity |
| Predicate | originOfSurnameVariant |
P16885
|
FINISHED |
| Object | anglicisation of Wesley |
—
|
LITERAL 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: anglicisation of Wesley | Statement: [House of Wellesley, originOfSurnameVariant, anglicisation of Wesley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfSurnameVariant Context triple: [House of Wellesley, originOfSurnameVariant, anglicisation of Wesley]
-
A.
languageOfSurnameVariants
Indicates the language in which particular surname variants are used or originate.
-
B.
surnameVariant
chosen
Indicates that one surname is an alternative spelling, form, or variation of another surname.
-
C.
EuropeanNameVariant
Indicates that one name is a variant or alternative form of another name as used in a European language or cultural context.
-
D.
familyNameOriginType
Indicates the type or source of origin associated with a person's family name.
-
E.
patronymicOrigin
Indicates that one entity’s name is derived from the name of a father or paternal ancestor of another entity.
- F. None of above.
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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 27, 2026, 1:40 a.m.