Triple
T14816244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophia Jagiellon |
E348323
|
entity |
| Predicate | royal role |
P25666
|
FINISHED |
| Object | daughter of the king of Poland |
—
|
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: daughter of the king of Poland | Statement: [Sophia Jagiellon, royal role, daughter of the king of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royal role Context triple: [Sophia Jagiellon, royal role, daughter of the king of Poland]
-
A.
royalFunction
Indicates a role, duty, or activity specifically associated with royalty or the exercise of royal authority.
-
B.
royalDuties
Indicates that an entity has responsibilities, obligations, or functions associated with a royal role or position.
-
C.
dynasticRole
chosen
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
-
D.
royalAppointment
Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
-
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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe2c1ec81908b3dff7a5d0e85d0 |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:49 a.m.