Triple
T9199934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adolphine Helmle |
E220810
|
entity |
| Predicate | positionInSpouseSequence |
P4764
|
FINISHED |
| Object | first wife |
—
|
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: first wife | Statement: [Adolphine Helmle, positionInSpouseSequence, first wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSpouseSequence Context triple: [Adolphine Helmle, positionInSpouseSequence, first wife]
-
A.
spouseOrder
chosen
Indicates the position or sequence of a person among multiple spouses in a marital relationship.
-
B.
positionOnMarriage
Indicates a person's stance, opinion, or policy regarding the institution or practice of marriage.
-
C.
positionHeldBySpouse
Indicates that a particular position, role, or office is or was held by the spouse of a given person.
-
D.
positionInFamilyBirthOrder
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
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_69ca83e8e9248190862cf3e41693b310 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd881c5d48190bbc33fac71a1d849 |
completed | April 1, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.