Triple
T2161219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Berlin (air campaign) |
E46804
|
entity |
| Predicate | primaryForceUsed |
P18776
|
FINISHED |
| Object | heavy bombers |
—
|
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: heavy bombers | Statement: [Battle of Berlin (air campaign), primaryForceUsed, heavy bombers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryForceUsed Context triple: [Battle of Berlin (air campaign), primaryForceUsed, heavy bombers]
-
A.
primaryForce
Indicates that one entity serves as the main or dominant force acting upon, influencing, or driving another entity or process.
-
B.
primaryForces
chosen
Indicates a relationship where one or more forces are identified as the main or dominant contributors to an effect, behavior, or outcome among all forces involved.
-
C.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
D.
primaryDamageType
Indicates the main kind of harm or injury that an action, event, or object is responsible for causing.
-
E.
primaryEnemyForces
Indicates that the related entities constitute the main opposing or hostile forces in a conflict or competitive situation.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe89e6ac8190b4b4bc0be4fe7aa9 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.