Triple
T20457585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Brandenburg |
E501834
|
entity |
| Predicate | maritalPolicyRole |
P99052
|
FINISHED |
| Object | dynastic marriage alliances |
—
|
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: dynastic marriage alliances | Statement: [Princess of Brandenburg, maritalPolicyRole, dynastic marriage alliances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalPolicyRole Context triple: [Princess of Brandenburg, maritalPolicyRole, dynastic marriage alliances]
-
A.
maritalPolicy
chosen
Indicates a relationship where an authority or institution defines rules, conditions, or norms governing marriage between individuals.
-
B.
hasMaritalFunction
Indicates that one entity serves a role or performs a function within the context of a marital relationship or institution.
-
C.
afterMarriageRole
Indicates the role or status an entity assumes following a marriage event.
-
D.
maritalBasis
Indicates that the relationship or status in question is founded on, justified by, or determined due to a marital relationship between the involved entities.
-
E.
spouseOfRole
Indicates that one role is the spouse (husband, wife, or equivalent marital partner) of another role.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a2a8a88190992211b09295d8ea |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.