Triple
T17001429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carmen Lasky |
E412452
|
entity |
| Predicate | spouseStartTime (Abraham Kaplan) |
P14428
|
FINISHED |
| Object | after 1964 |
—
|
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: after 1964 | Statement: [Carmen Lasky, spouseStartTime (Abraham Kaplan), after 1964]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseStartTime (Abraham Kaplan) Context triple: [Carmen Lasky, spouseStartTime (Abraham Kaplan), after 1964]
-
A.
spouseStartTime
chosen
Indicates the point in time when two individuals began their spousal (marriage) relationship.
-
B.
spouseEndTime
Indicates the time or date at which a spousal relationship between two entities ends.
-
C.
spouseEra
Indicates that two individuals are spouses during a specified historical period or era.
-
D.
metSpouseAt
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
-
E.
spouseOfficeEndTime
Indicates the time at which a spouse’s term or tenure in a particular office or position ends.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d37ec2b48190b4f997899d887ba8 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.