Triple
T13910062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Kent |
E334465
|
entity |
| Predicate | marriageRequirement |
P43165
|
FINISHED |
| Object | marriage to the Duke of Kent |
—
|
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: marriage to the Duke of Kent | Statement: [Duchess of Kent, marriageRequirement, marriage to the Duke of Kent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageRequirement Context triple: [Duchess of Kent, marriageRequirement, marriage to the Duke of Kent]
-
A.
marriageBefore
Indicates that one marriage event occurred earlier in time than another marriage event.
-
B.
marriageClauseCondition
chosen
Indicates that a specific condition or set of conditions related to a marriage clause must be satisfied for the associated legal or contractual effect to apply.
-
C.
ageAtMarriage
Indicates the age a person was when they got married.
-
D.
marriageProvision
Indicates that one party provides for, supports, or makes arrangements related to another party’s marriage (such as financial, legal, or material provisions).
-
E.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2723461881908376b5509ee0d530 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.