Triple
T15690051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rachel Menken |
E380303
|
entity |
| Predicate | seriesSettingPeriod |
P302
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Rachel Menken, seriesSettingPeriod, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesSettingPeriod Context triple: [Rachel Menken, seriesSettingPeriod, 1960s]
-
A.
settingPeriodDuration
Indicates the length of time for which a particular setting or configuration remains in effect.
-
B.
setsBaselinePeriod
Indicates that an entity establishes or defines a reference time span used as the baseline for comparison, measurement, or evaluation of subsequent periods.
-
C.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
E.
showsTimePeriod
Indicates that one entity presents or displays a specific span or interval of time associated with another entity.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f4e59988190aaf12f6a07c8f0e4 |
completed | April 16, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69deda8c856c8190882330114f9a1a5f |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:44 a.m.