Triple
T35825387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dux Legnicensis |
E1035627
|
entity |
| Predicate | countryInMedievalPeriod |
P10939
|
FINISHED |
| Object | Kingdom of Poland |
E86441
|
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: Kingdom of Poland | Statement: [Dux Legnicensis, countryInMedievalPeriod, Kingdom of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryInMedievalPeriod Context triple: [Dux Legnicensis, countryInMedievalPeriod, Kingdom of Poland]
-
A.
countryInIronAge
Indicates that a country existed and was culturally or technologically in the Iron Age during a specified historical period.
-
B.
medievalState
chosen
Indicates that an entity functioned as a state or political unit during the medieval historical period.
-
C.
countryDuringCrusades
Indicates that an entity functioned as or corresponded to a particular country during the historical period of the Crusades.
-
D.
countryDuring16thCentury
Indicates that an entity functioned as a country or sovereign political unit during the 16th century.
-
E.
countryDuringHabsburgPeriod
Indicates that a country existed under, was ruled by, or was part of the Habsburg realms during the historical Habsburg period.
- F. None of above.
Provenance (4 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0212b3462c8190ba3587852cb10655 |
completed | May 11, 2026, 5:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38ae1447d481908da23274b4f4ef7d |
completed | June 22, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_6a020f3138a48190ac630e810939e881 |
completed | May 11, 2026, 5:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.