Triple
T26539114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Whydah |
E671332
|
entity |
| Predicate | EuropeanNameVariant |
P161028
|
FINISHED |
| Object | Hueda |
—
|
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: Hueda | Statement: [Kingdom of Whydah, EuropeanNameVariant, Hueda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EuropeanNameVariant Context triple: [Kingdom of Whydah, EuropeanNameVariant, Hueda]
-
A.
EuropeanNameVariant
chosen
Indicates that one name is a variant or alternative form of another name as used in a European language or cultural context.
-
B.
languageOfSurnameVariants
Indicates the language in which particular surname variants are used or originate.
-
C.
surnameVariant
Indicates that one surname is an alternative spelling, form, or variation of another surname.
-
D.
hasEthnonymVariant
Indicates that one ethnonym is an alternative or variant form of another ethnonym referring to the same ethnic group.
-
E.
equivalentSurnameInGerman
Indicates that two surnames are equivalent to each other when translated into or represented in the German language.
- 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_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 1:40 a.m.