Triple
T24133764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | АН СССР |
E598024
|
entity |
| Predicate | подчинённость |
P258
|
FINISHED |
| Object | Совет Министров СССР |
—
|
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: Совет Министров СССР | Statement: [АН СССР, подчинённость, Совет Министров СССР]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: подчинённость Context triple: [АН СССР, подчинённость, Совет Министров СССР]
-
A.
subordinateTo
chosen
Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight of another entity.
-
B.
indicatesSubjugation
Indicates that one entity is under the domination, control, or authority of another, reflecting a hierarchical power imbalance or enforced obedience.
-
C.
надлежност
Indicates that one entity belongs to, is under the authority of, or falls within the responsibility or jurisdiction of another entity.
-
D.
imposedDominanceOf
Indicates that one entity has forcibly asserted control, authority, or superiority over another, typically without the latter’s consent.
-
E.
arity
Indicates the number of arguments or participants that a relation or function takes.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df79bfd08190970ed1b3f14ebc8b |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:26 p.m.