Triple
T20294408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Retrospect |
E510108
|
entity |
| Predicate | workPeriodCovered |
P116502
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [In Retrospect, workPeriodCovered, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workPeriodCovered Context triple: [In Retrospect, workPeriodCovered, mid-20th century]
-
A.
containsWorkFromPeriod
chosen
Indicates that something includes or features work that originates from a specified historical or temporal period.
-
B.
hasWorkPeriod
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
-
C.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
D.
hasWorkPeriodStart
Indicates the point in time when a specified work period begins.
-
E.
appearsInWorkRange
Indicates that an entity is featured or occurs within a specified range or subset of a larger work or collection of works.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67704262c8190bc903b733d849881 |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:13 a.m.