Triple
T20996654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanley Kubrick |
E517166
|
entity |
| Predicate | spouseEndTimeWithTobaMetz |
P34761
|
FINISHED |
| Object | 1951 |
—
|
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: 1951 | Statement: [Stanley Kubrick, spouseEndTimeWithTobaMetz, 1951]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseEndTimeWithTobaMetz Context triple: [Stanley Kubrick, spouseEndTimeWithTobaMetz, 1951]
-
A.
spouseEndTime
chosen
Indicates the time or date at which a spousal relationship between two entities ends.
-
B.
spouseOfficeEndTime
Indicates the time at which a spouse’s term or tenure in a particular office or position ends.
-
C.
spouseStartTime
Indicates the point in time when two individuals began their spousal (marriage) relationship.
-
D.
metSpouseAt
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
-
E.
metSpouseThrough
Indicates that one person became acquainted with and subsequently married their spouse as a result of a particular intermediary person, event, place, or context.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc21838081909872eed21bc12a08 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:51 p.m.