Triple
T34216081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Williams |
E877791
|
entity |
| Predicate | hasSpouseDeathEvent |
P95821
|
FINISHED |
| Object | Air Florida Flight 90 crash |
—
|
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: Air Florida Flight 90 crash | Statement: [Virginia Williams, hasSpouseDeathEvent, Air Florida Flight 90 crash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseDeathEvent Context triple: [Virginia Williams, hasSpouseDeathEvent, Air Florida Flight 90 crash]
-
A.
spouseDateOfDeath
Indicates the date on which a person's spouse died.
-
B.
spouseDeath
chosen
Indicates that one person's spouse has died, marking the event of the spouse's death in relation to that person.
-
C.
marriedToUntilDeathOfSpouse
Indicates a marital relationship that is intended to remain in effect until the death of one of the spouses.
-
D.
spouseDeathContext
Indicates the circumstances or contextual details surrounding the death of a person’s spouse.
-
E.
hasSpouseOfInterred
Indicates that one person is the spouse of an individual who is interred (buried or entombed).
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: May 1, 2026, 1:55 a.m.