Triple
T35170176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorothea of Pomerania |
E1015522
|
entity |
| Predicate | governanceFormContext |
P118045
|
FINISHED |
| Object | feudal 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: feudal duchy | Statement: [Dorothea of Pomerania, governanceFormContext, feudal duchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governanceFormContext Context triple: [Dorothea of Pomerania, governanceFormContext, feudal duchy]
-
A.
hasGovernanceForm
chosen
Indicates that an entity is organized or administered according to a particular system or form of governance.
-
B.
governingSystemContext
Indicates the broader political, legal, or organizational system within which an action, decision, or relationship is defined and regulated.
-
C.
governmentFormModeled
Indicates that one government form is modeled after, or structurally based on, another government form.
-
D.
governingForm
Indicates that one entity specifies or embodies the authoritative rules, structure, or format that control or regulate another entity.
-
E.
governanceRecord
Indicates that there exists a documented governance-related action, decision, or oversight event associated with the entities involved.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01b935e3948190a7af37b07938d618 |
completed | May 11, 2026, 11:10 a.m. |
| PD | Predicate disambiguation | batch_6a01b8d198b48190b01e16ac9ce7e7bd |
completed | May 11, 2026, 11:09 a.m. |
Created at: May 3, 2026, 4:02 p.m.