Triple
T38436585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 918th Bomb Group |
E903961
|
entity |
| Predicate | commandingOfficerInFiction |
P184389
|
FINISHED |
| Object | Frank Savage |
—
|
NE NERFINISHED |
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: Frank Savage | Statement: [918th Bomb Group, commandingOfficerInFiction, Frank Savage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandingOfficerInFiction Context triple: [918th Bomb Group, commandingOfficerInFiction, Frank Savage]
-
A.
commandingOfficers
Indicates that one entity serves as a commanding officer with authority over another entity.
-
B.
commandingFigureInStory
chosen
Indicates that one entity serves as a dominant, authoritative, or controlling figure within the narrative context of another entity’s story.
-
C.
commandingOfficerDuringEvents
Indicates that one entity served as the commanding officer of another entity during a specified set of events.
-
D.
commandingOfficerRank
Indicates the military rank held by the officer who has command authority over a given individual or unit.
-
E.
chiefOfGeneralStaff
Indicates that a person holds the position of Chief of the General Staff in relation to a specific military organization or armed forces.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:31 p.m.