Triple
T11914579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wendela |
E283481
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Wendelaer |
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: Wendelaer | Statement: [Wendela, hasVariant, Wendelaer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wendelaer Context triple: [Wendela, hasVariant, Wendelaer]
-
A.
Wendela
chosen
Wendela is a feminine given name of Dutch origin, historically associated with members of prominent Amsterdam patrician families.
-
B.
Trichardt
Trichardt is a small town in Mpumalanga, South Africa, known for its close association with the nearby industrial and coal-mining hub of Secunda.
-
C.
Welper
Welper is a district of the town of Hattingen in North Rhine-Westphalia, Germany.
-
D.
Wilsede
Wilsede is a small village in the Lüneburg Heath region of Lower Saxony, Germany, known for its well-preserved heathland landscape and traditional car-free character.
-
E.
Ehrwald
Ehrwald is a picturesque Austrian village in Tyrol, known as a popular alpine resort and gateway to the Zugspitze massif.
- 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_69f44014e1d08190ac7425f375ca023f |
completed | May 1, 2026, 5:54 a.m. |
Created at: April 8, 2026, 9:44 p.m.