Triple
T26585320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dobrawa of Bohemia |
E667192
|
entity |
| Predicate | associatedDynastyByMarriage |
P25212
|
FINISHED |
| Object | Piast dynasty |
—
|
NE NERFINISHED |
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: Piast dynasty | Statement: [Dobrawa of Bohemia, associatedDynastyByMarriage, Piast dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDynastyByMarriage Context triple: [Dobrawa of Bohemia, associatedDynastyByMarriage, Piast dynasty]
-
A.
spouseDynasty
chosen
Indicates that there is a marital relationship linking an entity to the dynasty (family line or ruling house) of their spouse.
-
B.
spouseOfMonarchsFamily
Indicates that one person is the spouse of a member of a monarch’s family.
-
C.
marriedToMonarchFrom
Indicates that a person is married to a monarch who rules or comes from a specified country or region.
-
D.
formedByMarriageOf
Indicates that something (typically a family, union, or legal entity) comes into existence as a result of the marriage between two entities.
-
E.
spouseOfRoyalHouse
Indicates that one entity is the spouse or consort of a member of a royal house.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
Created at: April 27, 2026, 2:05 a.m.