Triple
T29125996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 49th Fighter Group |
E738229
|
entity |
| Predicate | branchDuringWWII |
P126869
|
FINISHED |
| Object | United States Army Air Forces |
—
|
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: United States Army Air Forces | Statement: [49th Fighter Group, branchDuringWWII, United States Army Air Forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchDuringWWII Context triple: [49th Fighter Group, branchDuringWWII, United States Army Air Forces]
-
A.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
B.
enemyDuringWWII
Indicates that one entity was an enemy of the other during World War II.
-
C.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
D.
operatorDuringWorldWarII
chosen
Indicates that an entity operated or was active in its role during the period of World War II.
-
E.
frontDuringWWII
Indicates that an entity served as a military front or active combat theater during World War II.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6622a39d48190b2e3bda35831060a |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:28 a.m.