Triple
T13921515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piasts of Oświęcim |
E334755
|
entity |
| Predicate | houseStyle |
P4631
|
FINISHED |
| Object | Piast |
E347554
|
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: Piast | Statement: [Piasts of Oświęcim, houseStyle, Piast]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Piast Context triple: [Piasts of Oświęcim, houseStyle, Piast]
-
A.
Piast
chosen
Piast refers to the first historical ruling dynasty of Poland, which governed the Polish lands from the 10th century until the late 14th century.
-
B.
Piastów
Piastów is a small town in east-central Poland that functions as a residential suburb within the Warsaw metropolitan area.
-
C.
Bytom Piasts
The Bytom Piasts were a regional branch of the medieval Polish Piast dynasty that ruled the Duchy of Bytom in Upper Silesia.
-
D.
Rawa Piasts
Rawa Piasts were a regional branch of Poland’s medieval Piast royal family that ruled territories centered around Rawa Mazowiecka.
-
E.
Kuyavian Piasts
The Kuyavian Piasts were a regional branch of Poland’s early medieval Piast royal family that ruled parts of Kuyavia and neighboring lands.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa5c1f481908a9d8786872f08fe |
completed | April 14, 2026, 11:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7ce7c4a788190a1e7619a00ab0c2e |
completed | May 3, 2026, 10:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.