Triple
T11938492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Bismarck Sea |
E284112
|
entity |
| Predicate | forceTypeAllied |
P102252
|
FINISHED |
| Object | air forces |
—
|
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: air forces | Statement: [Battle of the Bismarck Sea, forceTypeAllied, air forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceTypeAllied Context triple: [Battle of the Bismarck Sea, forceTypeAllied, air forces]
-
A.
alliedForces
Indicates that multiple entities are cooperating militarily or strategically as part of the same alliance or coalition.
-
B.
alliedUnit
Indicates that one unit is associated as an ally or cooperative partner with another unit, typically sharing goals or working together.
-
C.
alliedNationForcesUnderCommand
Indicates that military forces from allied nations are operating under the authority or command structure of a specified commander or entity.
-
D.
UnionForcesType
Indicates that one entity is associated with, composed of, or characterized by a specific type or category of union forces.
-
E.
oftenAlliedWith
Indicates that one entity is frequently or habitually allied or aligned in cooperation with 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903415d2481909d84e6727454b9fe |
completed | April 10, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:45 p.m.