Triple
T8584905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Brief History |
E203280
|
entity |
| Predicate | workPeriodDescribed |
P7950
|
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: [My Brief History, workPeriodDescribed, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workPeriodDescribed Context triple: [My Brief History, workPeriodDescribed, mid-20th century]
-
A.
workPeriod
chosen
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
B.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
-
C.
workSettingPeriod
Indicates the time period during which a particular work setting or employment context is in effect.
-
D.
workDescribedIn
Indicates that a work (such as a publication or document) provides a description or account of the referenced entity.
-
E.
workDescribedAs
Indicates that one entity’s work, project, or output is characterized, labeled, or referred to by a particular description, title, or phrase.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:22 p.m.