Triple
T29573021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marie-Anne Dandonneau du Sablé |
E753360
|
entity |
| Predicate | spouseNobilityTitle |
P156461
|
FINISHED |
| Object | sieur de La Vérendrye |
—
|
NE NERFINISHED |
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: sieur de La Vérendrye | Statement: [Marie-Anne Dandonneau du Sablé, spouseNobilityTitle, sieur de La Vérendrye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseNobilityTitle Context triple: [Marie-Anne Dandonneau du Sablé, spouseNobilityTitle, sieur de La Vérendrye]
-
A.
spouseNobilityStatus
Indicates that the predicate specifies the nobility rank or noble status held by a person’s spouse.
-
B.
hasSpouseTitle
Indicates that a person’s spouse holds a particular title or honorific designation.
-
C.
spouseNameWithTitle
chosen
Indicates that a person’s spouse is identified by name together with an associated honorific or title.
-
D.
isSpouseOfTitle
Indicates that one entity holds a spousal relationship specifically associated with a titled or honorific status of another entity.
-
E.
spouseNameAfterEnnoblement
Indicates that the predicate specifies the spouse’s name as it is used after the spouse has been ennobled or granted a noble title.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 28, 2026, 6 p.m.