Triple
T13063577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabeau of Bavaria |
E329257
|
entity |
| Predicate | hasSpouseType |
P31663
|
FINISHED |
| Object | royal consort |
—
|
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: royal consort | Statement: [Isabeau of Bavaria, hasSpouseType, royal consort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseType Context triple: [Isabeau of Bavaria, hasSpouseType, royal consort]
-
A.
spouseType
chosen
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
B.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
-
C.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
D.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
-
E.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980e9bdfc81908eb90fb50597df64 |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 8:59 p.m.