Triple
T35299606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Bomba kryptologiczna |
E1019467
|
entity |
| Predicate | opposedCipherUser |
P437
|
FINISHED |
| Object | Nazi Germany |
—
|
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: Nazi Germany | Statement: [Polish Bomba kryptologiczna, opposedCipherUser, Nazi Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedCipherUser Context triple: [Polish Bomba kryptologiczna, opposedCipherUser, Nazi Germany]
-
A.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposedForcesUsers
Indicates a relationship where users are aligned with or represent opposing forces or sides in a conflict, competition, or struggle.
-
C.
opposedOperation
Indicates that one operation is in conflict with, counters, or works against another operation.
-
D.
opposesIdentity
Indicates that one entity actively rejects, resists, or stands in opposition to the identity, self-conception, or defining characteristics of another entity.
-
E.
otherAdversary
Indicates that one entity is an adversary of another, distinct from any primary or previously identified adversary.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:03 p.m.