Triple
T33986218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fay Maltese |
E871415
|
entity |
| Predicate | marriageEndToGeneHackman |
P193427
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [Fay Maltese, marriageEndToGeneHackman, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageEndToGeneHackman Context triple: [Fay Maltese, marriageEndToGeneHackman, 1986]
-
A.
marriageEndWithGeneWilder
chosen
Indicates that a marriage relationship concludes with Gene Wilder as one of the spouses at the point of its termination.
-
B.
endTime (marriage)
Indicates the point in time at which the marriage relationship is considered to have ended.
-
C.
resultedInMarriageTo
Indicates that one event, action, or circumstance led to or caused a marriage to occur between the related entities.
-
D.
marriageEndedBy
Indicates that a marriage relationship between two entities has been terminated due to the action or decision of a specified party or event.
-
E.
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).
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 1, 2026, 1:50 a.m.