Triple
T14740468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beatrix of Świdnica |
E346330
|
entity |
| Predicate | place of birth |
P1
|
FINISHED |
| Object | Świdnica |
—
|
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: Świdnica | Statement: [Beatrix of Świdnica, place of birth, Świdnica]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Świdnica Context triple: [Beatrix of Świdnica, place of birth, Świdnica]
-
A.
Świdnica
chosen
Świdnica is a historic town in southwestern Poland known for its well-preserved medieval architecture and the UNESCO-listed Church of Peace.
-
B.
Świdnik
Świdnik is a town in eastern Poland known for its aviation industry and proximity to the regional capital, Lublin.
-
C.
Glanów
Glanów is a village in southern Poland located within the administrative district of Gmina Trzyciąż in Lesser Poland Voivodeship.
-
D.
Cieszyn
Cieszyn is a historic town in southern Poland on the Olza River, known for its shared Polish-Czech heritage and well-preserved old town.
-
E.
Tarnów
Tarnów is a historic city in southern Poland known for its well-preserved Old Town, Renaissance architecture, and cultural heritage.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7345680819093e901233a064e48 |
completed | April 14, 2026, 11:01 p.m. |
Created at: April 10, 2026, 1:30 a.m.