Triple
T31192649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimson Dynamo |
E795222
|
entity |
| Predicate | primaryAffiliationInFiction |
P207372
|
FINISHED |
| Object | Soviet government |
E20452
|
NE 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 government | Statement: [Crimson Dynamo, primaryAffiliationInFiction, Soviet government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAffiliationInFiction Context triple: [Crimson Dynamo, primaryAffiliationInFiction, Soviet government]
-
A.
primaryAffiliation
Indicates the main organization, institution, or group with which an entity is chiefly associated or formally connected.
-
B.
isFictionalAgentOf
Indicates that one entity is a fictional character or agent that acts on behalf of, or represents, another entity.
-
C.
mainCharacterAffiliation
Indicates the group, organization, or side with which the main character is formally or primarily aligned.
-
D.
appearsInFictionAs
Indicates that one entity is depicted or represented as a character, figure, or element within a fictional work or narrative.
-
E.
characterAffiliationPortrayed
Indicates that a portrayal shows a character as being affiliated with a particular group, organization, or side.
- F. None of above. chosen
Provenance (5 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2959187fb081908dd9fbdaf5c30015 |
completed | June 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:08 p.m.