Triple
T33252189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martha Simms |
E851278
|
entity |
| Predicate | primarySettingPeriod |
P123135
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Martha Simms, primarySettingPeriod, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySettingPeriod Context triple: [Martha Simms, primarySettingPeriod, 1970s]
-
A.
mainSettingPeriod
chosen
Indicates the historical or temporal period in which the primary setting of a work or event takes place.
-
B.
primarySetting
Indicates that one entity serves as the main or central location, context, or environment in which the other entity’s events or activities primarily take place.
-
C.
primaryServicePeriod
Indicates the main or most significant span of time during which a service, duty, or activity is performed or in effect.
-
D.
primarySettingOf
Indicates that a location or context serves as the main or principal setting in which an entity (such as a story, event, or activity) takes place.
-
E.
primaryCollectionPeriod
Indicates the main time span during which data, items, or observations are initially collected or gathered.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:31 a.m.