Triple
T13521810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleśnica Piasts |
E322915
|
entity |
| Predicate | governmentFormOfDomain |
P56329
|
FINISHED |
| Object | duchy |
—
|
LITERAL 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: duchy | Statement: [Oleśnica Piasts, governmentFormOfDomain, duchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentFormOfDomain Context triple: [Oleśnica Piasts, governmentFormOfDomain, duchy]
-
A.
governmentalDomain
Indicates that one entity functions as the governmental sphere, jurisdiction, or area of authority within which another entity operates or is regulated.
-
B.
governmentFormDefined
Indicates that the specific form or structure of governance for an entity has been formally specified or classified.
-
C.
governmentalForm
chosen
Indicates the type or structure of governance that characterizes a political entity or organization.
-
D.
governmentFormUnder
Indicates that one governmental form or system operates under the authority, framework, or jurisdiction of another governmental form.
-
E.
formsGovernmentThrough
Indicates that one entity establishes or constitutes the governing authority or administration by means of another specified process, mechanism, or arrangement.
- F. None of above.
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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa3df0c8190804174695587f0ea |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:44 p.m.