Triple
T6073226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis Henri de Pardaillan de Gondrin |
E135335
|
entity |
| Predicate | spouseBecame |
P63278
|
FINISHED |
| Object | royal mistress of Louis XIV of France |
—
|
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 mistress of Louis XIV of France | Statement: [Louis Henri de Pardaillan de Gondrin, spouseBecame, royal mistress of Louis XIV of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseBecame Context triple: [Louis Henri de Pardaillan de Gondrin, spouseBecame, royal mistress of Louis XIV of France]
-
A.
spouseTransformedInto
chosen
Indicates that one spouse in a marital relationship has been changed or converted into a different form, state, or entity.
-
B.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
C.
marriedAfter
Indicates that one marriage occurred later in time than another specified marriage.
-
D.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
E.
spouseOfHead
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
- 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0575b9bc08190a78b3082b9ccf00c |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.