Triple
T4058870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Josefa Ortiz de Domínguez |
E84759
|
entity |
| Predicate | hasSpouseRole |
P26253
|
FINISHED |
| Object | wife of the corregidor of Querétaro |
—
|
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: wife of the corregidor of Querétaro | Statement: [Josefa Ortiz de Domínguez, hasSpouseRole, wife of the corregidor of Querétaro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseRole Context triple: [Josefa Ortiz de Domínguez, hasSpouseRole, wife of the corregidor of Querétaro]
-
A.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
B.
hasSpouseInStory
Indicates that one entity is depicted as the spouse of another within the context of a particular story or narrative.
-
C.
hasSpouseDescribed
chosen
Indicates that one entity is described as the spouse of another entity.
-
D.
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).
-
E.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbd13b4481908f9c09cc4f4a9724 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.