Triple
T21688681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsar Bomba test site |
E535299
|
entity |
| Predicate | testDeviceDesigners |
P184
|
FINISHED |
| Object | Soviet nuclear weapons designers |
—
|
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: Soviet nuclear weapons designers | Statement: [Tsar Bomba test site, testDeviceDesigners, Soviet nuclear weapons designers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testDeviceDesigners Context triple: [Tsar Bomba test site, testDeviceDesigners, Soviet nuclear weapons designers]
-
A.
productTypeDesigned
Indicates that one entity is the type or category of product for which another entity has been specifically designed.
-
B.
designerType
Indicates the specific kind or category of designer role associated with an entity.
-
C.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
D.
designedBy
chosen
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
E.
vendorDesignation
Indicates that one entity assigns or recognizes a specific vendor status, label, or role for another entity within a business or procurement context.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96cd51d481908df67e4f69826b06 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.