Triple
T9450519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Socialist Republics |
E227876
|
entity |
| Predicate | defenseControl |
P88247
|
FINISHED |
| Object | central Soviet authorities |
—
|
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: central Soviet authorities | Statement: [Soviet Socialist Republics, defenseControl, central Soviet authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenseControl Context triple: [Soviet Socialist Republics, defenseControl, central Soviet authorities]
-
A.
defenseLayer
Indicates a protective barrier or mechanism that shields an entity from harm, attack, or unwanted influence.
-
B.
defense
Indicates an action or relationship in which an entity protects, guards, or resists against a threat, attack, or criticism from another entity.
-
C.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
D.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
E.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
- 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_69ca8439f8bc8190997f2ef40c9f0bc2 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f6649a48190b6844daa6202efe5 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:51 p.m.