Triple
T27553873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lana Walsh |
E695581
|
entity |
| Predicate | spouseOfSequence |
P178587
|
FINISHED |
| Object | first wife of Terry Nichols |
—
|
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 of Terry Nichols | Statement: [Lana Walsh, spouseOfSequence, first wife of Terry Nichols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfSequence Context triple: [Lana Walsh, spouseOfSequence, first wife of Terry Nichols]
-
A.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
B.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
C.
spouseOfWork
Indicates that one person is the spouse of another specifically in the context of their workplace or professional environment.
-
D.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
-
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. chosen
Provenance (4 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 27, 2026, 1:36 p.m.