Triple
T12889904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted W. Lawson |
E308329
|
entity |
| Predicate | workDescribes |
P107288
|
FINISHED |
| Object | training and execution of the Doolittle Raid |
—
|
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: training and execution of the Doolittle Raid | Statement: [Ted W. Lawson, workDescribes, training and execution of the Doolittle Raid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workDescribes Context triple: [Ted W. Lawson, workDescribes, training and execution of the Doolittle Raid]
-
A.
workDescribedIn
Indicates that a work (such as a publication or document) provides a description or account of the referenced entity.
-
B.
workDescribedAs
Indicates that one entity’s work, project, or output is characterized, labeled, or referred to by a particular description, title, or phrase.
-
C.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
D.
describesCareerOf
Indicates that one entity provides a description or characterization of the professional career of another entity.
-
E.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714581988190afc720ffd7797860 |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:39 p.m.