Triple
T10699656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruth Evelyn Martin |
E252237
|
entity |
| Predicate | spouseActivePeriod |
P78262
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [Ruth Evelyn Martin, spouseActivePeriod, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseActivePeriod Context triple: [Ruth Evelyn Martin, spouseActivePeriod, 1930s]
-
A.
spouseStartTime
Indicates the point in time when two individuals began their spousal (marriage) relationship.
-
B.
maritalPeriodWith
chosen
Indicates the time span during which two entities were married to each other.
-
C.
roleDuringSpouseTenure
Indicates that a person held a particular role or position specifically during the period when their spouse was in office or serving in a defined tenure.
-
D.
spouseEndTime
Indicates the time or date at which a spousal relationship between two entities ends.
-
E.
spousePositionHeldStartTime
Indicates the date and time when a spouse first began holding a particular position or office.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd8abd7c81909c274aa1699a3695 |
completed | April 9, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.