Triple
T28973199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 301st Fighter Squadron |
E734332
|
entity |
| Predicate | primaryEnemyForcesEngaged |
P4675
|
FINISHED |
| Object | Luftwaffe |
—
|
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: Luftwaffe | Statement: [301st Fighter Squadron, primaryEnemyForcesEngaged, Luftwaffe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEnemyForcesEngaged Context triple: [301st Fighter Squadron, primaryEnemyForcesEngaged, Luftwaffe]
-
A.
primaryEnemyForces
Indicates that the related entities constitute the main opposing or hostile forces in a conflict or competitive situation.
-
B.
primaryEnemy
chosen
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
C.
primaryOpposingForceSize
Indicates the size or magnitude of the main opposing force acting against a subject in a given context.
-
D.
engagedForces
Indicates that one force has actively committed or deployed its military units against another force in combat or operational interaction.
-
E.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a009d623f6c8190b702e2892c52fbb2 |
completed | May 10, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_6a009a3050d48190b64567f28e6ea463 |
completed | May 10, 2026, 2:46 p.m. |
Created at: April 28, 2026, 9:07 a.m.