Triple
T14124781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cieszyn Piasts |
E339999
|
entity |
| Predicate | sharesOriginWith |
P3438
|
FINISHED |
| Object | Opole Piasts |
E309926
|
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: Opole Piasts | Statement: [Cieszyn Piasts, sharesOriginWith, Opole Piasts]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Opole Piasts Context triple: [Cieszyn Piasts, sharesOriginWith, Opole Piasts]
-
A.
Opole Piasts
chosen
The Opole Piasts were a regional branch of Poland’s Piast dynasty that ruled the Duchy of Opole and surrounding Silesian territories during the Middle Ages.
-
B.
Sandomierz Piasts
The Sandomierz Piasts were a regional branch of Poland’s early medieval Piast royal family that ruled the Sandomierz region as part of the fragmented Piast monarchy.
-
C.
Inowrocław Piasts
The Inowrocław Piasts were a regional branch of Poland’s early medieval Piast royal family that ruled the Inowrocław area.
-
D.
Żagań Piasts
Żagań Piasts were a Silesian branch of the medieval Polish Piast royal dynasty that ruled the Duchy of Żagań.
-
E.
Racibórz Piasts
The Racibórz Piasts were a regional branch of Poland’s medieval Piast dynasty that ruled the Duchy of Racibórz in Silesia.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6096976481909dc79066c5165a50 |
completed | April 14, 2026, 3:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd7a2fdd7c8190b2ebf5a18c8039f2 |
completed | May 8, 2026, 5:52 a.m. |
Created at: April 9, 2026, 10:22 p.m.