Triple
T15001774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Bigamy |
E374107
|
entity |
| Predicate | targetedForce |
P116305
|
FINISHED |
| Object | Axis forces in North Africa |
—
|
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: Axis forces in North Africa | Statement: [Operation Bigamy, targetedForce, Axis forces in North Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedForce Context triple: [Operation Bigamy, targetedForce, Axis forces in North Africa]
-
A.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
B.
navalForceTargeted
Indicates that a naval force is selected or designated as the target of an action or operation.
-
C.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
D.
targetedBecauseOf
Indicates that one entity is made a target of an action, harm, or scrutiny specifically due to possessing a particular attribute, identity, or characteristic.
-
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. 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded72fec948190b1c9705538c57976 |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:54 a.m.