Triple
T35025516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margaret of Pomerania |
E1010323
|
entity |
| Predicate | royal house as queen |
P139262
|
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: [Margaret of Pomerania, royal house as queen, Piast dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royal house as queen Context triple: [Margaret of Pomerania, royal house as queen, Piast dynasty]
-
A.
royalHouseAsQueen
chosen
Indicates that a person serves or has served as queen within a specified royal house or dynasty.
-
B.
reignAsQueenConsort
Indicates that a person holds the position and performs the role of queen consort during the reign of a monarch.
-
C.
reignAsQueenConsortFrom
Indicates the time period during which a person held the role of queen consort, starting from a specified date or event.
-
D.
royalHouseOfMother
Indicates the dynastic or royal family to which an individual's mother belongs.
-
E.
royalMistressOf
Indicates that one person is the (typically unofficial) romantic or sexual partner of a royal figure, such as a king or prince.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.