Triple
T29114861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 389th Bombardment Group |
E737015
|
entity |
| Predicate | forceAssignment |
P166346
|
FINISHED |
| Object | Eighth Air Force |
—
|
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: Eighth Air Force | Statement: [389th Bombardment Group, forceAssignment, Eighth Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceAssignment Context triple: [389th Bombardment Group, forceAssignment, Eighth Air Force]
-
A.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
B.
requiresAssignment
Indicates that one entity depends on another entity being assigned or allocated before it can proceed, function, or be considered valid.
-
C.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
D.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
E.
forceStructure
Indicates a relationship where one entity imposes or defines the structural arrangement, organization, or configuration of another entity.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661ef9e2481908788797adbd5c937 |
completed | May 2, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:21 a.m.