Triple
T12952610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bytom Piasts |
E309927
|
entity |
| Predicate | governmentTypeOfDomain |
P220
|
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: [Bytom Piasts, governmentTypeOfDomain, duchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentTypeOfDomain Context triple: [Bytom Piasts, governmentTypeOfDomain, 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.
governmentType
chosen
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
C.
governmentTypeStrengthened
Indicates that the form or structure of a government has been reinforced, consolidated, or made more powerful or stable relative to its previous state.
-
D.
governmentTypeSupported
Indicates that an entity endorses, backs, or is in favor of a particular form or system of government.
-
E.
governmentTypeServed
Indicates the type of government that an entity serves, is affiliated with, or operates under in its role or function.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.