Triple
T22152337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbertien dynasty |
E547443
|
entity |
| Predicate | maritalStrategy |
P99052
|
FINISHED |
| Object | intermarriage with royal and princely houses |
—
|
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: intermarriage with royal and princely houses | Statement: [Herbertien dynasty, maritalStrategy, intermarriage with royal and princely houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalStrategy Context triple: [Herbertien dynasty, maritalStrategy, intermarriage with royal and princely houses]
-
A.
maritalPolicy
chosen
Indicates a relationship where an authority or institution defines rules, conditions, or norms governing marriage between individuals.
-
B.
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.
-
C.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
D.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
E.
maritalPeriodWith
Indicates the time span during which two entities were married to each other.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f4b05c8190a824f55804f6d4d5 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.