Triple
T1787973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Oyelowo as Martin Luther King Jr. |
E39430
|
entity |
| Predicate | workSettingPeriod |
P32393
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [David Oyelowo as Martin Luther King Jr., workSettingPeriod, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workSettingPeriod Context triple: [David Oyelowo as Martin Luther King Jr., workSettingPeriod, 1965]
-
A.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
B.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
C.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
D.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
E.
workScope
Indicates the defined range, extent, and boundaries of tasks or responsibilities involved in a particular work activity or project.
- F. None of above. chosen
Provenance (4 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab75444d28819091c393e62fc97f82 |
completed | March 7, 2026, 12:45 a.m. |
Created at: March 4, 2026, 7:32 p.m.