Triple
T702590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RKKA |
E14029
|
entity |
| Predicate | politicalOrgan |
P4853
|
FINISHED |
| Object | political commissar system |
—
|
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: political commissar system | Statement: [RKKA, politicalOrgan, political commissar system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalOrgan Context triple: [RKKA, politicalOrgan, political commissar system]
-
A.
politicalOrganization
Indicates that an entity is a political organization, such as a party, movement, or group engaged in political activities or governance-related objectives.
-
B.
politicalForm
Indicates the type or structure of governance or political organization that characterizes an entity.
-
C.
politicalFunction
chosen
Indicates that an entity holds, performs, or is associated with a specific role, duty, or function within a political system or structure.
-
D.
politicalParty
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
-
E.
representedPoliticalEntity
Indicates that one entity has served as an official political representative or agent acting on behalf of another political entity.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58d4c3c8190ad4527d14bca5e6e |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4edc33881909a978268f6dd5d82 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.