Triple
T11914577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wendela |
E283481
|
entity |
| Predicate | linguisticForm |
P6520
|
FINISHED |
| Object | Wendela |
E283481
|
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: Wendela | Statement: [Wendela, linguisticForm, Wendela]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wendela Context triple: [Wendela, linguisticForm, Wendela]
-
A.
Wendela
chosen
Wendela is a feminine given name of Dutch origin, historically associated with members of prominent Amsterdam patrician families.
-
B.
Wandzia
Wandzia is a Polish diminutive form of the female given name Wanda, used as an affectionate or familiar nickname.
-
C.
Moingwena
The Moingwena were a Native American group historically associated with the Illinois (Illiniwek) confederation in the central Mississippi River region.
-
D.
Wenteche
Wenteche are an indigenous Mapuche subgroup traditionally inhabiting inland valleys and foothill regions of south-central Chile.
-
E.
Tandi
Tandi is a small town in Himachal Pradesh, India, known as a key junction in the Lahaul region where major mountain rivers meet and as a common stopover for travelers in the Himalayas.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e52a2bc08190b80cc6ccf5779d7c |
completed | April 10, 2026, 11:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f4186938548190b5ae10e111aece9a |
completed | May 1, 2026, 3:05 a.m. |
Created at: April 8, 2026, 9:44 p.m.