Triple
T9167846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henrietta Keller |
E220007
|
entity |
| Predicate | marriageOrderRelativeToAlJolson |
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: [Henrietta Keller, marriageOrderRelativeToAlJolson, first wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageOrderRelativeToAlJolson Context triple: [Henrietta Keller, marriageOrderRelativeToAlJolson, first wife]
-
A.
marriageOrderToClarkGable
Indicates the chronological position in which an entity married Clark Gable relative to his other spouses.
-
B.
marriageSequenceToHussein
Indicates that an entity enters into a marriage with Hussein at a specific point or order within a sequence of marriages.
-
C.
spouseOrder
chosen
Indicates the position or sequence of a person among multiple spouses in a marital relationship.
-
D.
marriageResolvedBy
Indicates that a marital relationship between two parties has been formally concluded or dissolved through a specific resolving action or process (e.g., divorce, annulment).
-
E.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaadfb50881909b9127f92e4b3e21 |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.